Threading

I think WaitCursor should be on its own thread as anything which takes a little time on the main thread pauses the WaitCursor.

I know you should not do anything which blocks the main thread but sometimes its not practical to create worker threads for every little operation which only takes a second or two.

Hello Henda79,

thank you for your post. WaitCursor was designed with the following idea:
To amuse the user while a background operation is taking place. When the background operation finishes, you should hide the WaitCursor.

All the graphical output has to be done on the main thread. It is not possible to perform any graphical output from a worker thread. So even if we wanted to, the architecture of Windows OS does not allow us to implement your idea.

I understand that creating a background thread for even the "little" operations can be bothersome, on the other hand you will have a super responsive application

Best regards
Vladimir Gregor
Bee Mobile | Skype ID: beemobile_support | Phone: +421 94 88 99 22 9 | Email: support at beemobile4 dot net

Yes, I thought of that problem when I had posted the topic