Feature request: (un)install keyboard hook on (tcp?) demand #860
Labels
enhancement
New feature or request
llhook
Pertains to the standard version of Kanata on Windows
PRs welcome
jtroo has no plans to work on this at present, but PRs are welcome
windows
Issue pertains to Windows only
Is your feature request related to a problem? Please describe.
Currently the order of keyboard hooks installed by various apps can't be predetermined. This introduces hard-to-avoid conflicts, making it hard to use, for example, AutoHotkey and kanata side-by-side.
Describe the solution you'd like.
aunch kanata in a "waiting-to-start-a-hook" mode, where it sets up all the processing machinery, but doesn't actually install the keyboard hook.
Then on some external activation even, for example, a message sent via TCP: 1) "activate layer_with_kbd_hook_F", 2) "F is down" 3) "exit on F up" kanata would:
layer_with_kbd_hook_F
layerf key down
event to the loop so that kanata's state machine is aware of itGiven that the latest installed keyboard hook has priority, this should be more reliable for that timing the launches of various apps since those apps can also (un)install hooks dynamically
Describe alternatives you've considered.
My other idea was to maybe use kanata as a lib when it supports #816
Additional context
No response
The text was updated successfully, but these errors were encountered: