StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8594203
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-12-21T17:56:55.953
FavoriteCount
0
LastActivityDate
2011-12-21T17:56:55.953
LastEditDate
LastEditorUserId
0
OwnerUserId
244795
ParentId
7770781
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
You've started out from the wrong implementation: you shouldn't make a <code>CFormView</code> with a <code>CTabCtrl</code> and then stuff more <code>CFormView</code>s into it. This isn't going to work right. Instead, you should work with <code>CPropertySheet</code> and <code>CPropertyPage</code>, where focus handling has already been taken care of. You will still be able to access the <code>CTabCtrl</code> owned by the <code>CPropertySheet</code> by calling <code>GetTabControl()</code>, but MFC will take care of the problems you've encountered. Briefly: derive classes from <code>CPropertySheet</code> for each of the dialog windows you want to show (e.g., CConfigPage1, CConfigPage2). Create a Dialog resource in the Resource Editor for each of them, and do all of the other standard <code>CDialog</code> setup. Next, derive a class from <code>CPropertySheet</code> (e.g., CProps), and (optionally) handle WM_SIZE and TCN_SELCHANGE. Finally, derive a class from a CView descendent, like <code>CScrollView</code> (e.g., CViewMyAwesomeStuff). Then add member variables for the <code>CPropertySheet</code> and <code>CPropertyPage</code>s, and handle WM_CREATE where you Add() each page to the property sheet and then <code>Create(this,WS_CHILD|WS_VISIBLE)</code> the property sheet. Bonus: You can forward the <code>CView::OnUpdate</code> to each child <code>CPropertyPage</code> by calling <code>GetPage()</code> in a loop and calling a function on each of them, or you can send a message to each of them (use a user-defined message, like <code>WM_APP+1</code>). They can discover their parent's <code>CDocument</code> by calling <code>GetParent()->GetParent()->GetDocument()</code>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POTab Order with CTabCtrl and child CFormViews
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USuser244795
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.