Hi,

 I sorted out the problem using BackGroundWorker component that is avaliable from .NET. I tried to use ThreadManager, but somehow I couldn't simulate the same way like BackgroundWoker component.

 It seems we need a separate thread. We cannot display WaitWindow on the same thread.

 Thanks

Raja

 

No.  The wait window will behave the same in this environment as it does on any other form.  When you say that you are not able to show the Wait Window, are you receiving an exception?  Try placing a button on a form and calling the ShowWaitWindow to see if it appears.  If you are calling the WaitWindow on a separate thread then you will need to either invoke it on the main thread or ensure that it is called within the same thread in which you are working.  That would be the only thing I could think of that would cause it not to show.

Hi,

 I am also doing the same and also tried the example from the help. I am not able to Show the Wait window.

 Having said that , Does WaitWindow behave differently when you work in a MDI window?

That is the only difference from what I am doing.

Indira

Excellent... let me know one way or another.  Thanks.

Yeah, they are ThreadAbortExceptions. I'll give the latest release a try and see if it clears up.

Thanks.

Robin Giltner

Are the problems you're having unexpected ThreadAbortExceptions?  Likely thrown within the WndProc for WM_PAINT messages?  If so, we've made changes to fix that very issue.  You should be able to go to the posted updates forum from the board home and find the latest version that will fix that very issue. 

Now, if that's not your issue, you might need to expound upon what it is.  At the moment, there's no way to prevent the wait window from using the fade effect... it always fades in/out.

I'm trying to troubleshoot some problems we are having with Threads on forms that employ the waitwindow.  How might I go about turning off the fade in/out effect.

I couldn't find any property about it, or do I need to override one of the methods ?

Thanks

Robin Giltner

Most likely, the problem is coming from the way that the wait window is being shown... all showing and unshowing of the WaitWindow must be done on the main thread of the application (the UI thread) through synchronization to avoid cross-thread exceptions.  By default, the WaitWindow fades in rather than just poping in, so, if you're doing all of your work on the main thread rather than a side thread, the main thread does not have time to process the fading in/out of the WaitWindow.  So, you might try to set the WaitWindow to show immediately, rather than fade in/out, or start up a background thread that shows the wait window, processes the information and then hides the wait window, allowing the main thread time to hide and show the wait window.

Hope that helps...

Hello Keith,







sorry, maybe I expressed something wrong: I meant _not_ that it is working with a sleep(5000). But one can see that the waitWindow will arise 5 seconds after that sleep, as long as the 'HideWaitWindow()' is commented out or deleted, excluded from executing.



If a HideWaitWindow() is executed, the waitWindow will never be shown.



Seems like the sleep(...) will let sleeping the system, preventing the waitWindow from becoming visible, and the HideWaitWindow()-command will hide a waitWindow never seen...



HTH,



best regards, Ralph

Thanks Ralph, I had given up on Wait Window.... Ill give this a shot. Though I do need it to work with a sleep() of less than 5000










Keith Chisarik