Skip to content
This repository has been archived by the owner on Mar 23, 2020. It is now read-only.

[Feature Request] API for disabling / enabling keys #12

Open
evilC opened this issue Feb 13, 2019 · 1 comment
Open

[Feature Request] API for disabling / enabling keys #12

evilC opened this issue Feb 13, 2019 · 1 comment

Comments

@evilC
Copy link

evilC commented Feb 13, 2019

It would be nice to be able to programatically enable / disable sending of key events (For a specific key) via an API.
Use case:
Being able to turn on/off blocking of keys while they are in analog mode, for example so you can type in a chat box
For example, I may have some code which uses pixel detection to detect when the chat box is active and enable the keys that are currently disabled, without having to try and infer it from keypresses, or have the user hit a special key to turn key blocking on/off.

@cactysman
Copy link

cactysman commented Feb 27, 2019

Other examples would be games running / rendering on the keyboard that take input.
This way you could prevent the current active window from getting random inputs (that control that game) or accidental actions performed by those keystrokes.

For still being able to access keystrokes, some event / callback should be made available.


In order to prevent abuse of this feature, something like holding the Mode key could maybe re-enable all the keys that were blocked with the SDK.
Furthermore, disabling the A1, A2, A3, Mode keys should not be allowed in the first place.

Along with a function to disable a single key, a function to toggle a whole array of keys (just like in the RGB SDK) should be made available aswell.

Thoughts?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants