--- In [email protected], "swzoh" <[EMAIL PROTECTED]> wrote: > I guess the monitor script has If()Do-EndIf. So, if they are mixed up, > it would look like this chronologically: > > If()Do > ... > For() > ,,, > Wait.For() > ... > EndIf <--- Error message popped up here, I guess > ,,, > EndFor
There seems to be a problem with Wait.For(). ----------------- Test1.PowerPro ---------------------------- If(1)Do Wait.For(2000) EndIf ------------------------------------------------------------- ---------------- Test2.PowerPro ----------------------------- For(!ctrl) Win.Debug(2) EndFor ------------------------------------------------------------- Execute Test1 & Test2 in this order, nearly simultaneously. Then exit the for by pressing ctrl after 2 seconds passed. Open the Test1.PowerPro in a text editor. My text editor (g)vim gives an warning that the file is read-only, i.e., in use. Strangely, there is no problem like this if using Wait.Until(). And, if the order of the execution of the two scripts are reversed, no problem either even with Wait.For(). Sean 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/
