-
Notifications
You must be signed in to change notification settings - Fork 6.6k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[launcher] - Win+R seems to conflict with WW #2035
Comments
Same for AutoHotkey and macros bound to Win+C or Win+B. If the key combindation is pressed, the action is done. If the key is released, Window Walker pops up. Example macro: #b::
IfWinNotExist, ahk_exe firefox.exe
{
Run C:\Program Files (x86)\Mozilla Firefox\firefox.exe
WinWait ahk_exe firefox.exe
}
WinActivate
return |
If I understand correctly @crutkas, this only happens when Power Launcher is up right? Since we are going to be working to move this into Power Launcher, the launch bugs won't matter that much. We will see how much progress I can make this weekend. |
Yes. But I am very interested in why this is happening. Which code base is the offending as it could impact other apps. |
This is happening because of the code in the shell plugin. The Shell plugin has it's own code to override the Win+R key and because of the way they are creating and handling hooks (not completely sure how they're doing it), once we press Win+R, the To unblock us and mitigate this issue for now, I tried to use the BackSpace keystroke instead of Control, so we would be simulating a @ryanbodrug-microsoft, @betsegaw and @crutkas any thoughts? I understand the proper way would be to figure out how they're handling hooks and why they're facing this issue. |
Our keystroke override code should be a single spot. i would remove the wox code path IMO. |
I've put in a hack for now by simulating the |
When I execute Win+R, launcher doesn't stay open and it also tries to open WW. When I hold Win+R, it keeps the search box open but starts to open shortcut guide and window walker
workaround is to disable WW.
The text was updated successfully, but these errors were encountered: