StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1629724
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-10-27T09:49:20.427
FavoriteCount
0
LastActivityDate
2009-10-27T09:49:20.427
LastEditDate
LastEditorUserId
0
OwnerUserId
76116
ParentId
1558932
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
It seemed to be something to do with the mouse capture!? The normal sequence of events during a drag goes something like this... <ol> <li>The <code>PreviewMouseLeftButtonDown</code> handler gets called and <code>ListBox.IsMouseCaptureWithin</code> is false.</li> <li>The <code>PreviewMouseMove</code> handler gets called. By this time <code>ListBox.IsMouseCaptureWithin</code> is true.</li> <li>During the <code>PreviewMouseMove</code> handler <code>DragDrop.DoDragDrop</code> gets called and sometime during this the mouse capture is released from the ListBox.</li> </ol> But, what seems to happening for a drag started when the context menu is open is... <ol> <li>The <code>PreviewMouseLeftButtonDown</code> handler gets called and <code>ListBox.IsMouseCaptureWithin</code> is false.</li> <li>The <code>PreviewMouseMove</code> handler gets called. But this time <code>ListBox.IsMouseCaptureWithin</code> is still false.</li> <li>Sometime after the end of the <code>PreviewMouseMove</code> handler the ListBox then gets the mouse capture (<code>ListBox.IsMouseCaptureWithin</code> becomes true)</li> </ol> The result of this is that after the drag, the ListBox still has the mouse capture so any clicks on the button to open the context menu are actually going to the listbox not the button. Adding the following code to the start of the <code>PreviewMouseLeftButtonDown</code> handler seems to help by swallowing up the click that closes that context menu rather than trying to start a drag from it... <pre><code>if (!contextMenuCloseComplete) { sourceElement.CaptureMouse(); return; } </code></pre> ...with the <code>contextMenuCloseComplete</code> bool getting set in handlers for the context menu's <code>Closed</code> and <code>Opened</code> events. Does that make sense? Does anyone understand where this mouse capture behaviour is coming from?
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWPF ListBox drag & drop interferes with ContextMenu?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USIanR
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWPF ListBox drag & drop interferes with ContextMenu?
 singulars
 PostTypePostTypeId
 PTQuestion
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
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.