StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14176797
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-01-05T21:52:49.433
FavoriteCount
0
LastActivityDate
2013-01-05T22:17:40.550
LastEditDate
2013-01-05T22:17:40.550
LastEditorUserId
981238
OwnerUserId
1943428
ParentId
8792164
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
This post has been useful to me also, although my case was slightly different. In this case avoiding <code>_currentForm.Hide();</code> works fine because the code does a form-switch. I found that the problem also originates with a MDIChild that has been hidden by a different MDIChild that is on top. Here's a workaround that works also in that case based on the fact that <code>Dispose</code> is always called. It can be done preparing something like this: <pre><code>public abstract class FormExtenderClass : Form{ private bool formClosingFired = false; private bool formClosedFired = false; protected override void OnFormClosing(FormClosingEventArgs e) { base.OnFormClosing(e); formClosingFired = !e.Cancel; } protected override void OnFormClosed(FormClosedEventArgs e) { base.OnFormClosed(e); formClosingFired = true; } protected override void Dispose(bool disposing) { if (!formClosingFired) OnFormClosing(new FormClosingEventArgs(CloseReason.UserClosing, false)); if (!formClosedFired) OnFormClosed(new FormClosedEventArgs(CloseReason.UserClosing)); base.Dispose(disposing); } } </code></pre> Then in the code of MDIChildren just change the first row from <pre><code>public partial class AutoForm : Form { </code></pre> to <pre><code>public partial class AutoForm : FormExtenderClass { </code></pre> Consider that is in any case a worarkound. The main difference is that set <code>e.Cancel=true</code> will have no effect in the case that <code>FormClosing</code> is called from Disposed as backup.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POFormClosing Event not called for MDI Child Form
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USmjk
UserOwnerUserId
1. USDiego Mazzaro
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
 VTApproveEditSuggestion
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.