Marco van den Oever

@TechnicallyJoe Do you have any thoughts on how the window selection should work?

@TechnicallyJoe Not sure if you're aware, but there is an alpha build available of WTQ v2, where this behavior is partially implemented: https://github.com/flyingpie/windows-terminal-quake/releases/tag/v2.0.0-pre3 And the accompanying discussion: https://github.com/flyingpie/windows-terminal-quake/discussions/119 If you're...

Hopefully one of the provided solutions have helped. I've added some of the problems found to the [docs](https://wtq.flyingpie.nl). If the problem persists, feel free to re-open this issue, or open...

@BlueDrink9 Thank you for reporting this issue! What keyboard layout are you using?

@BlueDrink9 No worries, just happy that you took the time to report the issue!

@hnstcK Yes! Here's an example: ```jsonc { "Apps": [ { "Name": "WezTerm", "Hotkeys": [{ "Modifiers": "Super", "Key": "D1" }], // (...) } ] } ``` Does that work for you?

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...

@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. ```jsonc { "Features": { "SharpHook": true } } ``` Additionally, there has...

The new hotkey system, using [SharpHook](https://github.com/TolikPylypchuk/SharpHook) has been the new default since v2.0.16, and fully supports the "Windows" (or "Super", or "Meta") modifier.