| Groups | Blog | Home |
dotnet windows forms : Dialog ghost left on window
Hello,
I have a Systems.Windows.Forms.Form-based window. When I bring up a dialog to modify the window's view and click OK, the dialog goes away, except the part of the dialog that overlaps the window remains visible until the window repaints. Is there a way to fix this? If there is a lot of processing in calculating the new view, it is rather unattractive to have part of the dialog still visible for several seconds. I can do this: dlg.ShowDialog(); if (System.Windows.Forms.DialogResult.OK == dlg.DialogResult) { // call update on the ApplicationForm // call a method on the dialog to change the view dlg.SetNewView(); } dlg.Dispose(); This is unsatisfying, since the user of the dialog has to make two additional calls; I'd like for all the processing to take place in the dialog class when the user clicks OK. TIA for any ideas...
This is happening because your parent windows is not receiving a Paint
message. This will not happen until your process completes running. This is a draw back of Single Threaded windows forms applications. Everything runs on the UI thread. The best way to get rid of this problem is to run your process on a secondary thread. This will allow the Main windows to receive the necessary Paint messages while your process is running. Here is a reply from a posting I made a while back that helped me with this exact same situation. <<== First, in your Button.Click event handler, for your 10 min routine, does it wait in some OS function(like synchronize Device I/O function) or just stay in a long processing loop? If your Button.Click event handler just fall in a user mode long processing loop, I suggest you call Application.DoEvents() method in each loop, this method will peek all the messages(including WM_PAINT message) from current thread message queue, then process it. It will give your application a responsive UI. If your Button.Click event handler is waiting in OS function synchronize operation such as Device I/O, I think we should use multithreading, just place the long processing device I/O code in another worker thread. Then our UI main thread will not be blocked, and we will have responsive UI. In ..Net, we can achieve this with asynchronize delegate, for more information, please refer to Chris Sells' great article: "Safe, Simple Multithreading in Windows Forms, Part 1" http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnforms/htm l/winforms06112002.asp ==> -- - Thanks, Steven Perry [quoted text, click to view] "Developer" wrote:
> Hello, > > I have a Systems.Windows.Forms.Form-based window. When I bring up a dialog > to modify the window's view and click OK, the dialog goes away, except the > part of the dialog that overlaps the window remains visible until the window > repaints. > > Is there a way to fix this? If there is a lot of processing in calculating > the new view, it is rather unattractive to have part of the dialog still > visible for several seconds. > > I can do this: > > dlg.ShowDialog(); > > if (System.Windows.Forms.DialogResult.OK == dlg.DialogResult) { > // call update on the ApplicationForm > // call a method on the dialog to change the view > dlg.SetNewView(); > } > > dlg.Dispose(); > > This is unsatisfying, since the user of the dialog has to make two > additional calls; I'd like for all the processing to take place in the > dialog class when the user clicks OK. > > TIA for any ideas... > >
Thanks for the reply, Steven.
In my dialog's OnClosed handler, I'm doing this: // This should invalidate the ApplicationForm... this.Owner.Update(); // This should allow the ApplicationForm to tell its children to update... Application.DoEvents(); // Calc the new view and change the display... SetNewView(); base.OnClosed(e); Unfortunately, it doesn't work; the dialog is still left on the document window. I've started experimenting with the thread technique in the linked article, but that hasn't worked yet, either. C. [quoted text, click to view] "Steven Perry" <dotsperrynet@nospam.nospam> wrote in message news:ED1991E6-3A09-4C6E-853A-41996C67A180@microsoft.com... > This is happening because your parent windows is not receiving a Paint > message. This will not happen until your process completes running. This > is > a draw back of Single Threaded windows forms applications. Everything > runs > on the UI thread. > > The best way to get rid of this problem is to run your process on a > secondary thread. This will allow the Main windows to receive the > necessary > Paint messages while your process is running. > > Here is a reply from a posting I made a while back that helped me with > this > exact same situation. > > <<== > First, in your Button.Click event handler, for your 10 min routine, does > it > wait in some OS function(like synchronize Device I/O function) or just > stay > in a long processing loop? If your Button.Click event handler just fall in > a user mode long processing loop, I suggest you call > Application.DoEvents() > method in each loop, this method will peek all the messages(including > WM_PAINT message) from current thread message queue, then process it. It > will give your application a responsive UI. > > If your Button.Click event handler is waiting in OS function synchronize > operation such as Device I/O, I think we should use multithreading, just > place the long processing device I/O code in another worker thread. Then > our UI main thread will not be blocked, and we will have responsive UI. In > .Net, we can achieve this with asynchronize delegate, for more > information, > please refer to Chris Sells' great article: > "Safe, Simple Multithreading in Windows Forms, Part 1" > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnforms/htm > l/winforms06112002.asp > ==> > -- > - > Thanks, > > Steven Perry > > > "Developer" wrote: > >> Hello, >> >> I have a Systems.Windows.Forms.Form-based window. When I bring up a >> dialog >> to modify the window's view and click OK, the dialog goes away, except >> the >> part of the dialog that overlaps the window remains visible until the >> window >> repaints. >> >> Is there a way to fix this? If there is a lot of processing in >> calculating >> the new view, it is rather unattractive to have part of the dialog still >> visible for several seconds. >> >> I can do this: >> >> dlg.ShowDialog(); >> >> if (System.Windows.Forms.DialogResult.OK == dlg.DialogResult) { >> // call update on the ApplicationForm >> // call a method on the dialog to change the view >> dlg.SetNewView(); >> } >> >> dlg.Dispose(); >> >> This is unsatisfying, since the user of the dialog has to make two >> additional calls; I'd like for all the processing to take place in the >> dialog class when the user clicks OK. >> >> TIA for any ideas... >> >> >>
It seems that OnHandleDestroyed is the place to do the processing.
Validate the user's selection(s) in buttonAccept_Click. In OnHandleDestroyed, if DialogResult == DialogResult.OK, change the view. [quoted text, click to view] "Steven Perry" <dotsperrynet@nospam.nospam> wrote in message news:ED1991E6-3A09-4C6E-853A-41996C67A180@microsoft.com... > This is happening because your parent windows is not receiving a Paint > message. This will not happen until your process completes running. This > is > a draw back of Single Threaded windows forms applications. Everything > runs > on the UI thread. > > The best way to get rid of this problem is to run your process on a > secondary thread. This will allow the Main windows to receive the > necessary > Paint messages while your process is running. > > Here is a reply from a posting I made a while back that helped me with > this > exact same situation. > > <<== > First, in your Button.Click event handler, for your 10 min routine, does > it > wait in some OS function(like synchronize Device I/O function) or just > stay > in a long processing loop? If your Button.Click event handler just fall in > a user mode long processing loop, I suggest you call > Application.DoEvents() > method in each loop, this method will peek all the messages(including > WM_PAINT message) from current thread message queue, then process it. It > will give your application a responsive UI. > > If your Button.Click event handler is waiting in OS function synchronize > operation such as Device I/O, I think we should use multithreading, just > place the long processing device I/O code in another worker thread. Then > our UI main thread will not be blocked, and we will have responsive UI. In > .Net, we can achieve this with asynchronize delegate, for more > information, > please refer to Chris Sells' great article: > "Safe, Simple Multithreading in Windows Forms, Part 1" > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnforms/htm > l/winforms06112002.asp > ==> > -- > - > Thanks, > > Steven Perry > > > "Developer" wrote: > >> Hello, >> >> I have a Systems.Windows.Forms.Form-based window. When I bring up a >> dialog >> to modify the window's view and click OK, the dialog goes away, except >> the >> part of the dialog that overlaps the window remains visible until the >> window >> repaints. >> >> Is there a way to fix this? If there is a lot of processing in >> calculating >> the new view, it is rather unattractive to have part of the dialog still >> visible for several seconds. >> >> I can do this: >> >> dlg.ShowDialog(); >> >> if (System.Windows.Forms.DialogResult.OK == dlg.DialogResult) { >> // call update on the ApplicationForm >> // call a method on the dialog to change the view >> dlg.SetNewView(); >> } >> >> dlg.Dispose(); >> >> This is unsatisfying, since the user of the dialog has to make two >> additional calls; I'd like for all the processing to take place in the >> dialog class when the user clicks OK. >> >> TIA for any ideas... >> >> >>
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |