StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8990489
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-01-24T16:35:16.213
FavoriteCount
0
LastActivityDate
2012-01-24T16:35:16.213
LastEditDate
LastEditorUserId
0
OwnerUserId
1166346
ParentId
8840497
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
You can treat DialogBox as a complex comprised from several logical parts: <ol> <li>Loading dialog definition resource;</li> <li>Creating the dialog window which is accomplished internally via several calls to CreateWindow: the first for the dialog itself and then for its controls found in the template;</li> <li>Blocking owner window to support "modality" and running a message pump: GetMessage -> IsDialogMessage or TranslateMessage+DispatchMessage.</li> </ol> Speaking metaphorically this combination is useful when the flow of your program must branch depending on user's decision, encapsulating that decision into the single call to the DialogBox() function. This function really does a lot of work and eases the understanding of your program by hiding asynchronous nature of interaction with raw Win32 windows. However, this 'high-levelness', specifically the message loop contained within it, may actually raise the complexity of your program, if it already Win32 has message loop and the call to DialogBox is made as a response to a specific message. So in this case you have to take care about nested message loops, especially if you are custom message processing in your main message loop. In order to avoid such problems, CreateDialog function can be used which is also a complex but only of parts 1 and 2 - it doesn't start message loop. So, you have to provide your own message processing procedure. You should also take care about modality if it is required. In my practice I used DialogBox only several times for really small utility applications.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat is the right thing to do, DialogBox or CreateWindow
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USArty
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. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThe nested messages are a pain: I found few people among even those "experienced" in WinAPI realized about how functions were silently 'reentred', thus overwriting the previous context data. This can lead to very interesting kind of bugs... My take on it is to avoid adding message loops above the one already existing.
 singulars
 PostPostId
 PO
 UserUserId
 USpaercebal

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.