> > Yes, a WAIT.For tests every 5 ms. Unless Bruce writes a variation
> try
> >
>
> If the wait were much longer, PowerPro would be unresponsive.
> I could
> try a 20 ms or so wait to see what will happen in the next beta.
Well, the wait I'm doing is for a window with a caption telling me a
conversion is finished (mp3 converting - high cpu usage already). What I
needed was something to check every couple seconds. I'm using Ted's
workaround right now, which is working well enough. I'd hate to have
powerpro checking for a caption every 20ms even.
If there was something like:
Wait.for(n,expression[,n])
Where the second n says evaluate expression every x ms that would let you do
longer waits without the cpu intensity. Eg.
Wait.for(3600000,anywindow("=notepad"),2000)
Is going to wait for 1 hour, checking for the =notepad window every 2
seconds.
The third parameter changes how powerpro times and waits for things?
David Troesch | Atlanta, GA | ICQ# 2333123
What's happening to America, is big business killing it?
http://tinyurl.com/4weom
Funstuff: Computer Lie #12: Youll never use all that disk space.
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/
