--- In [email protected], "brucexs" <[EMAIL PROTECTED]> wrote: > > --- In [email protected], "Brian" <[EMAIL PROTECTED]> > wrote: > > > > --- In [email protected], "Brian" > <[EMAIL PROTECTED]> > > wrote: > > > back the focus. I tried having a monitor script that kept a > > > I have got this to work by using TweakUI to set a delay on the > XMouse of about 100ms. This is the delay between the time the mouse > passes over a window and the time the window is activated. You may > have to use a larger value.
Thank you. Actually, I was able to get it to work with a delay as low as 10 ms. > > YOu also have to make the PowerPro commands refer to the active > window, not the window under the mouse (which is the PowerPro bar). > > The trick is that, by active window, PowerPro means the window that > was active before the bar you clicked on. How does PowerPro know > which window this is? What is does is this. As soon as the mouse > passes over a bar, PowerPro is sent a message by Windows. PowerPro > uses the receipt of this message to note what the active window is, > just in case you click the bar. That way it knows the active window > before it. This works fine with no XMouse. But XMouse with no > delay breaks this, since the bar is activated as soon as the mouse > passes over it. Putting in the delay gives PowerPro a chance to > record the currently active window. Thank you very much for the explanation! When explained like that it becomes obvious what the problem is. Thank you very much. Brian Cunningham 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/
