--- In [email protected], "swzoh" <[EMAIL PROTECTED]> wrote: > > --- In [email protected], "brucexs" <bswitzer@> wrote: > > > > > It is referring to Sean's script and the line with the endfor. > > > I never use wait.until. The script was simply interfering with my > > > monitor list. Also no waits in there, though. > > > I think for-loops like this are just not such a good idea. > > > > I would agree that events could also work. Butt he for loop should > > work. I do suspect there are some issues when for loops have waits > > and another script runs during the wait. > > > > Does your monitor command list have a for loop? > > Does it call a script file? > > Does that script file have a for loop? > > I suspected the error check routine of If()Do which somehow became to > mix up different scripts when for loops have wait.for(), so, > exec.NoIfDoCheck would resolve it, at least for a while.
Sorry, it may not If()Do, but nested For()-EndFor and If()Do-EndIf error check routine. I recalled after the post that the example in the below message used to produce an error message even while I have exec.NoIfDoCheck: http://groups.yahoo.com/group/power-pro/message/28055 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/
