I forgot that a temporary second PowerPro process would be launched when using a PowerPro command line. This is probably when all of the second instances are created.
Someday I may dig around to see if I have any HookWindowEvents that also run scripts that run a PowerPro commandline (whew). I would wager this is true. I use many PowerPro commandlines to avoid nesting script calls too deeply or to help with Windows timing issues. ppBang shouldn't be creating a second process. A higher limit to HookWindowEvents should fix my missed events. Thank you, Ted >> FYI, I have noticed that sometimes, before the limits, I've >> had 2 processes of PowerPro running at the same time. I never >> discovered if this was due to HookWindowEvents or ppBanging >> around. I do have WAIT.For() in one of my WindowPlacement >> scripts called by HookWindowEvents for a couple of fussy programs. > > > I don't know how ppbang works. It is possible to create multiple > processes momentarily if you run a command line: the second one > just calls the first to execute the command line then it exits. > > --- brucexs wrote: > I don't think wait or hookwindowevents can create new processes. > 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/
