System.Windows.Input, LowLevelKeyboardProc and NHotkey, InputSimulator used to support shortcut, it should be unified.GlobalKeyboardEvent in IPublicAPI should be removed. The only place to set hotkey should be Settings.xamlBackKeyDownEvent in IPublicAPI should also be removed?System.Windows.Input for hotkey when Wox is focused.LowLevelKeyboardProc for all global hotkeyRelated issue
ideally there should be one solution
ref:
https://gist.github.com/Stasonix/3181083
https://blogs.msdn.microsoft.com/alejacma/2010/10/14/global-hooks-getting-lost-on-windows-7/
http://stackoverflow.com/questions/27181125/how-to-hook-win-tab-using-lowlevelkeyboardhook
https://msdn.microsoft.com/en-us/library/windows/desktop/ms644985(v=vs.85).aspx
currently GlobalKeyboardEvent always returns true in my machien, which cause sometimes win+r is not intercept correctly...
but it returns correctly in other machines #690
strange....
https://github.com/Wox-launcher/Wox.Plugin.Switcheroo/issues/6 may also releated
LowLevelKeyboardProc:
- [ ] Win key hotkey will trigger windows start menu if you release win key (instead of non modifier key ) first
1. if we ignore key up event like [1.3.105], then it will cause https://github.com/Wox-launcher/Wox.Plugin.Switcheroo/issues/6#issuecomment-222382709
2. this also happens on alt key for firefox as reported here
https://github.com/Wox-launcher/Wox/issues/707#issuecomment-222361380
if 2 is a mistake, could we just ignore win key up event?
LowLevelKeyboardProc:
this could be solved by use run as administrator
http://stackoverflow.com/questions/27335011/some-windows-in-windows-8-prevent-my-low-level-keyboard-hook-from-working
e.g.
win+r won't works when task manager is focused for 1.3.67
I suggest reverting commit eeb8310 , as it introduced so many bugs without fixing any issue.
btw, I'm working on #703 , I have found the reason, and I'm trying to find a elegant solution
the solution in commit eeb8310 is the only way to handle all kinds of hotkeys, I can't find other ways...
I'm working on #703 , I have found the reason
what's the reason?
I'm not proficient in the way handle hotkeys in windows, but for me the way in version 1.3.100 works quite well, except #703 ( I'm close to fix this issue), while I didn't find any advantages (any case that 103 can handle but 100 cannot) ojf the way to handle hotkeys in 1.3.103.
advantage:
1 you can't use win key as wox hotkey
2 #346 wants to double tap one of the modifier keys... (not working now, but possible with current solution)
trigger时不光通过唤起wox后输入关键词,还能直接通过快捷键唤起(例如现在的cmd插件支持win+R。再举一个场景,这个功能配合一些词典类的plugin,就能够取代一些字典软件了)
3 ability to support this feature you mentioned
well, then we have no choice but fix these bugs step by step...
@jhdxr 试一下 114?
LowLevelKeyboardProc, then #706 won't be fixed even we use black magic code like AttachThreadInput (in win10)NHotkey which use RegisterHotkey. then #706 won't happenLowLevelKeyboardProc as a fallback method to handle win keyInputSimulator to send alt+space to get focus instead of call focus method directly? no, InputSimulator use virtual key, so wox won't get focus too.there are so many code related, we need make an small app test ideas instead of refactoring wox directly....
how to disable registered hotkey
http://superuser.com/questions/129191/is-there-any-way-to-disable-certain-keyboard-shortcuts-in-windows-7
disable alt+tab
[HKEY_CURRENT_USERControl Panel\Desktop]
"CoolSwitch"="0"
👍 for this.
Win+Space would be nice to have
I suggest using hotkey ctrl + enter to run app as administrator.
Most helpful comment
I suggest using hotkey ctrl + enter to run app as administrator.