Re: Cannot use this type of wait in nested script

"brucexs-/[email protected] [power-pro]" <[email protected]>
Newsgroups gmane.comp.windows.power-pro
Message-ID <[email protected]>
This message is produced if PPro sees that some other script is running when the wait is processed.  It usually happens due to nesting, but it could also happen eg if there is an event or hot key or some other reason that Windows has re-entered PPro code so that the wait is executed while another script is running.
 

 

 I am afraid this is not something I can look into without a reliable way for me to reproduce it consistently.
 

 I suggest a different trying kind of wait as detailed in the help on waits.  
 PowerPro has many different ways of waiting. None handles all cases. You need to choose the wait most appropriate for your circumstances. Here is a summary of the kinds of waits: 
 wait for - can wait on many circumstances, as detailed below. Can be used anywhere and in any script situation. Multiple outstanding waits can exist, but only the last executed one is monitored; when it completes, the next to last is monitored, and so on.

 wait until - can wait on many circumstances, as detailed below. Cannot be used in nested scripts (a script which is called from another script). Multiple outstanding waits can exist and each is monitored independently. Cannot be used in Do() function.

 event plugin - can be used in any circumstances and many independent events can be outstanding. However, the event plugin is complex to use, especially when a wait in the middle of a script is needed.

 file.runwait and file.runcallback from the file plugin can be used in the special case where you want to run a program and wait for it to finish before doing other command Most of the time, the wait for command should be considered. Use wait until or an event plugin call if you need multiple outstanding waits of greatly different duration or conditions which must act independently.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.