flyingpie
[Hotkeys] "Windows" modifier is not working
My current settings under "Hotkey" are:
[
{
"Modifiers": "LWin",
"Key": "OemTilde"
},
{
"Modifiers": "Windows",
"Key": "Z"
},
{
"Modifiers": "Control",
"Key": "OemTilde"
}
]
Using this, control+~ works, but neither win+z or win+~ work.
Version 1.1.1, Win 10 Home
@BlueDrink9 Thank you for reporting this issue! What keyboard layout are you using?
Colemak. Switching to EN US (qwerty) might fix, but I currently can't start the app. Posted another issue about it.
Hmm, I redownloaded the app and re-extracted it, and this is now fixed. Sorry for wasting your time
@BlueDrink9 No worries, just happy that you took the time to report the issue!
@hnstcK Yes! Here's an example:
{
"Apps": [
{
"Name": "WezTerm",
"Hotkeys": [{ "Modifiers": "Super", "Key": "D1" }],
// (...)
}
]
}
Does that work for you?
Hey, no that's not working, running on windows with eurkey layout (https://eurkey.steffen.bruentjen.eu/start.html)
Mm, I'm having trouble finding the issue, but I'll look into this more.
It seems that the Windows modifier has some special treatment going on, but I'm not sure how to deal with it yet.
@hnstcK I've got a dev release where this problem should be fixed.
Could you take a look, see if it fixes the problem on your end too?
https://github.com/flyingpie/windows-terminal-quake/releases/tag/vDevSharpHook
The "SharpHook" hotkey registration has been put behind a feature flag, as it is quite an impactful change.
{
"Features": {
"SharpHook": true
}
}
Additionally, there has already been an issue with the new method, namely that bringing a window to the foreground doesn't always work properly.
This issue has also been seen with the upcoming API (to send commands to WTQ for scripting), and has to do with Windows not always allowing processes to bring a window to the foreground.
It's being worked on in this PR: https://github.com/flyingpie/windows-terminal-quake/pull/197.