Nothing wrong with using Wait.For() except it is more CPU intensive
than an event...
Wait.For(300000, ANYWINDOW("=notepad"))
IF(ANYWINDOW("=notepad"))DO
; launch your programs
ENDIF
An event is less CPU intensive at startup:
EVENT.Create(10,30, ESC("event.destroythis\n",?"\")++ ;;+
".YourScript", ?#ANYWINDOW("=notepad")# )
The above event launches YourScript.txt when a "notepad.exe" exists.
You could substitute VISIBLEWINDOW for ANYWINDOW; and substitute
a "caption" or "c=ClassNameOfProgram" for "=notepad".
The above event is tested 30 times in 5 minutes where the Wait.For is
tested 60,000 times in 5 minutes...
Ted
--- In [email protected], Barry Shaw wrote:
> Are there any issues with using waits in a startup script? I have a
> couple programs which I need to make sure start up after something
> else is loaded, and in a particular order. Is there a better way to
do
> this then using a script set to run at startup?
>
> --
>
> Sue Chastain
------------------------ Yahoo! Groups Sponsor --------------------~-->
Fair play? Video games influencing politics. Click and talk back!
http://us.click.yahoo.com/T8sf5C/tzNLAA/TtwFAA/JV_rlB/TM
--------------------------------------------------------------------~->
Attention: PowerPro's Web site has moved: http://www.ppro.org
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/power-pro/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
