C# - Alternative to Thread.Sleep?

Question

I\'m doing all this in C#, in Visual Studio 2008.

I want to slow down the work of my algorithm so that the user can watch it\'s work. There is a periodic change visible

Answer 1

I'd guess everything is running out of a single thread. The user probably invokes this algorithm by clicking on a button, or some such. This is handled by your main thread's message queue. Until this event handler returns, your app's GUI cannot update. It needs the message queue to be pumped on regular basis in order to stay responsive.

Sleeping is almost never a good idea, and definitely not a good idea in the GUI thread. I'm not going to recommend that you continue to use sleep and make your GUI responsive by calling Application.DoEvents.

Instead, you should run this algorithm in a background thread and when it completes it should signal so to the main thread.

Answer 2

This depends on a lot of things, so its hard to give a concrete answer from what you've said. Still, here are some matters that might be relevant:

Are you doing this on a UI thread (e.g. the thread the form-button or UI event that triggered the work started on)? If so, it may be better to create a new thread to perform the work.

Why do you sleep at all? If the state related to the ongoing work is available to all relevant threads, can the observer not just observe this without the working thread sleeping? Perhaps the working thread could write an indicator of the current progress to a volatile or locked variable (it must be locked if it's larger than pointer size - e.g. int or an object - but not otherwise. If not locked, then being volatile will prevent cache inconsistency between CPUs, though this may not be a big deal). In this case you could have a forms timer (there are different timers in .Net with different purposes) check the status of that variable and update the UI to reflect the work being done, without the working thread needing to do anything. At most it may be beneficial to Yield() in the working thread on occasion, but its not likely that even this will be needed.

Answer 3

First off, don't make the user wait for work that is done before they even think about when it will be finished. Its pointless. Please, just say no.

Second, you're "sleeping" the UI thread. That's why the UI thread is "locking up." The UI thread cannot be blocked; if it is, the UI thread cannot update controls on your forms and respond to system messages. Responding to system messages is an important task of the UI thread; failing to do so makes your application appear locked up to the System. Not a good thing.

If you want to accomplish this (please don't) just create a Timer when you start doing work that, when it Ticks, indicates its time to stop pretending to do work.

Again, please don't do this.

Answer 4

You are about to commit some fairly common user interface bloopers:

• Don't spam the user with minutiae, she's only interested in the result
• Don't force the user to work as fast as you demand
• Don't forbid the user to interact with your program when you are busy.

Instead:

• Display results in a gadget like a ListBox to allow the user to review results at her pace
• Keep a user interface interactive by using threads
• Slow down time for your own benefit with a debugger