Application Security Testing: An Integral Part of DevOps
It works like a:
While (Now < waitTill) : DoEvents : Wend
- loop but doesn't eat up all your system time like the above loop.
Why not use the Timer Control?
Well first, the timer control ist limited to a maximum 65 second intreval while this timer can handle intervals up to 2147483647 ms (that's just a bit less that 25 days).
Second: with a timer control it is difficult to so something like this:
..code runs ...
... continue code ..
Third: This class has a Cancel method to stop waiting a once.
Why should you use the Timer control?
CWaitNDispatch can do some unpretty things to your callstack when running. When you call wait on a timer object and then call wait on another while the first one is still running, the second one won't return until the "first" one has finnished. (See the example in the form).
When you call Cancel from a messagehandler (i.e. Command1_Click, Form_Unload) the code after the "Wait" call will continue AFTER you leave the message handler!
So don't call cancel in the Unload event because your app will not terminate then.
Call Cancel in QueryUnload and set the Cancel parameter of QueryUnload to true if timer.IsWaiting returns true.