Bruce, I've never had a problem with no limits to HookWindowEvents, but with the upper limit set where it is now I'm missing events. Nothing bad happens, just missing my events.
Question: Could you add a global variable that you initialize for most users, but we could modify? eg. _gHookWindowEventsLimit_=5. Maybe at zero, HookWindowEvents would be deactivated, and we could set and test higher upper limits. Thanks, Ted PS 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. --- brucexs wrote: > > - set upper limit to reentering hookwindowevents > > This is all I am planning for 4.3. If there are no major bugs > reported, I will create a release candidate in a week of so. 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/
