Re: Final Word (?) on Timers
- From: erewhon@xxxxxxxxxx (J French)
- Date: Wed, 25 Apr 2007 13:52:49 GMT
On Wed, 25 Apr 2007 08:44:53 -0500, Steve Kelley
<skelley@xxxxxxxxxxxxxxxxxxxxx> wrote:
Yet another option is to have a timer on the form and set the time out
value to 120000(ms) and enable it when the first batch file runs and run
the second batch file when the timer fires. You can disable your UI
elements to keep the user from interacting with your form until the
second batch file runs if needed. This way your system is not at all
tied down by any loop. This isn't technically a pause because your
program can keep processing after the timer is enabled but depending on
you your code is structured this may be OK.
Maybe - but I like the UI reacting
You really need to look into WaitMessage - it is a Lodestone
(Windows is really a cheat, so using the same tricks is .. well kind
of elegant)
.
- Follow-Ups:
- Re: Final Word (?) on Timers
- From: Steve Kelley
- Re: Final Word (?) on Timers
- References:
- Final Word (?) on Timers
- From: termv
- Re: Final Word (?) on Timers
- From: John Blessing
- Re: Final Word (?) on Timers
- From: J French
- Re: Final Word (?) on Timers
- From: Steve Kelley
- Final Word (?) on Timers
- Prev by Date: Re: Final Word (?) on Timers
- Next by Date: Re: Threads in Visual Basic?
- Previous by thread: Re: Final Word (?) on Timers
- Next by thread: Re: Final Word (?) on Timers
- Index(es):
Relevant Pages
|
