-
Notifications
You must be signed in to change notification settings - Fork 322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
getmouselocation doesn't modify window stack, why not? #118
Comments
Having getmouselocation set the window stack is a lovely idea! On Tuesday, May 10, 2016, alaricljs notifications@github.com wrote:
|
I would like this too. Mainly to be able to use |
Following up -- I ran into this today. For a workaround, I'm doing this until we have this command modify the windowstack:
|
This allows you to do 'getmouselocation windowactivate' for example, to activate the window the mouse is currently hovering over. Add docs about getmouselocation updating the window stack. Fixes #118
#322 addresses this. |
This allows you to do 'getmouselocation windowactivate' for example, to activate the window the mouse is currently hovering over. Add docs about getmouselocation updating the window stack. Fixes #118
This allows you to do 'getmouselocation windowactivate' for example, to activate the window the mouse is currently hovering over. Add docs about getmouselocation updating the window stack. Fixes jordansissel#118
I have a macro and I am trying to work around a Java bug with 'focus follows mouse' Basically The focus doesn't always follow the mouse. For the macro to work I am expecting the output to land on the window that is under the mouse so I tried getmouselocation but it doesn't modify the window stack for some reason. It returns the window ID, but that can't be used w/ search. Using the window id for send doesn't work either for your own noted reasons.
Can getmouselocation be made to set the window stack? On the other hand, why is it a random scattering of commands that can use a window id and not all of them?
The text was updated successfully, but these errors were encountered: