On Thu, 5 Apr 2007 06:58:45 -0400, "Gardner, Paul G." <[EMAIL PROTECTED]> wrote:
> >I stay away from HookWindows. Every time I use it, I get in trouble, and I >don't customize my machine so heavily that PP native abilities don't cover >what I need. > >HTH >Paul > Hm, just to add to my previous post, I'm not sure that PowerPro can actually detect the Sygate windows. Maybe it's not a case of Sygate loading before PowerPro after all. The reason why I say this is that I've just been experimenting. Rather than having PowerPro run a script when the Sygate window opens, I set it to "Position 1 1". I then opened up the Sygate console itself (it's not the window I want the AutoIt script to run against, however it has the word Sygate in the window title, so I thought this would be a good test to see if the command list actually worked). Nothing happened. PowerPro did not re-position the window. I then tried mintotray instead of position. Same thing - PowerPro did nothing to the window. Is there any way of telling if a window is something that PowerPro cannot detect? I know that AutoIt cannot detect all Windows controls (for example, it cannot detect Windows Control Panel windows), so I was thinking that maybe PowerPro had the same limitation. My command was Sygate* in the name field. I also tried with =smc.exe (the Sygate .exe file) in the name field. Same thing happened - PowerPro did nothing to the Sygate window. -- Regards, CM
