Before we simply called a delegate on the form the WaitWindow control was instantiated on to update the text as to what is happening, but kept running into a Threading error (discussed earlier here at http://forum.strataframe.net/Topic10242-7-1.aspx ).  The only fix I've found for that is to either not update the waitwindow from the foreground thread, or simply set the affinity on the applications process to only use 1 core/cpu etc.  We opted to go for the not updating the waitwindow from the foreground thread.

And now we are back to somehow indicating to the user that actions are still ongoing, the simple waitwindow isn't enough, so I was wanting to possibly pick you guys brains about what you may have done for this.

Adding something as simple as a Knight Rider bar would suffice, just something that would keep moving etc to let the user know the application hadn't locked up.

Or perhaps the animated elipses at the end of the WaitWindow title perhaps ?

We have thought about simply creating our own WaitWindow and using that, but yours is so nice and shiny  , and we would have a lot of code to change.

Any ideas ?

Thanks

Robin Giltner

The other option would be to use a progress bar on a status bar (if you have a status bar in your application).  You could simply show the progress bar on Marquee settings and keep it visible as long as the wait window is shown.

For operations that require a long time to process and we need a progress update back to the user, we created our own progress window for PracticeStudio.NET.  We use it and/or the wait window depending upon scenario.

Thanks.

Robin Giltner

I'm just throwing out ideas...