Update: I staggered the events by making them each run 1 second after the prior event, so they do not all run at the same time. PP CPU usage now does not exceed 3%
--- In [email protected], "Stuart" <[EMAIL PROTECTED]> wrote: > > My mistake. The events do continue through reconfigure. > > I now have one script file that creates 12 events - 2 events for each > of 6 buttons, each button corresponding to a program > > first event for each button is - if program is running and background > color is not "running color", change color to "running color" > > second event for each button is - is program is not running and > background color is not "not running color", change color to "not > running color" > > Rather than use autorun and destroy the events, I run the script at > startup and let it run all day, as I am using various of the 6 programs > all day. > > Each event runs every 10 seconds. PP CPU pops up to ~10% each time the > events run, but I don't notice it at all. Big difference from the > monitor script, which would push PP CPU to 15-20% or higher every > second or two. > > Thanks for your help, and thanks again for this great program. > > > > --- In [email protected], "brucexs" <bswitzer@> wrote: > > > > --- In [email protected], "Stuart" <smalis@> wrote: > > > > > > Bruce, thanks, that works well. Only problem is if I configure and > > > refresh PP, it ends the event. Is there a way to run a PP command > > > when PP is refreshed (which is different from startup)? > > > > > > Reconfiguring should not end events; possibly the envent is calling a > > command list which is changed? > > > > There is a facility to run a command list called Reconfigure each > time > > you OK out of pproconf.exe (see Setup|advanced|configure) but you > > should not need it.... > > >
