Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bind Arbitrary Keys #881

Closed
ranenvious opened this issue May 5, 2023 · 2 comments
Closed

Bind Arbitrary Keys #881

ranenvious opened this issue May 5, 2023 · 2 comments

Comments

@ranenvious
Copy link

Is your feature request related to a problem? Please describe.
There are a substantial number of keys that can be handled and processed like expected but are not present on most keyboards, allowing them to be safely bound to shortcuts and other actions without using keyboard real-estate. Prime examples of these keys would be F12-20 which are on no keyboards that I am aware of, yet are perfectly valid keys that can be used to trigger shortcuts.

Describe the solution you'd like
Ideally some method of binding any arbitrary key to a mouse button without having to physically press that key on your keyboard. In lieu of that though, even just a dropdown in the Macro Creator menu that lets you select from just F12-20 would be a massive help. (and let's be honest, most mice don't have more than 8 buttons that you'd want to rebind anyhow)

Describe alternatives you've considered
You could list F12-20 in the "Special Mapping" section, but I worry that would greatly bloat the menu and make it noticably more cumbersome to use. Another option is making a dedicated menu for binding abnormal keys, perhaps just below the "Send keystroke" menu.

@staticssleever668
Copy link
Member

NOTE: you can do this with ratbagctl - the command line interface for libratbag.
For example: ratbagctl Glorious button 5 action set key KEY_F18 (On Glorious Model O it seems that you can bind F13-F18 only, if you try to set F19-F24, the mouse seems to send KEY_RESERVED instead).

@staticssleever668
Copy link
Member

I think this can be considered a duplicate of #567.

@staticssleever668 staticssleever668 closed this as not planned Won't fix, can't repro, duplicate, stale May 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants