-
Notifications
You must be signed in to change notification settings - Fork 80
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
Allow arbitrary scancodes #857
Comments
Great news, thanks for coming up with this way of making it workable. |
Can we find if there is some software that could deduce the scancodes needed, e.g. by using the custom keys on a laptop and the software telling the scancodes received? We could then recommend this software for finding out the scancodes needed as that can be an endeavour in itself because a lot of manufacturers don't document them anywhere. E.g. "To add custom scancode, run this software, press the custom key on your laptop and use the received scancode in UHK Agent". |
@laxu To my knowledge, every OS does some sort of abstraction under the hood that makes user space applications unable to retrieve this information, and so, no such software exists. |
On linux there's Of course, if some sort of laptop firmware translates its specific scancodes on too low abstraction level, it might not tell you anything. |
The technique explained at https://jacksautohotkeyblog.wordpress.com/2016/04/14/understanding-autohotkey-keyboard-scan-codes-and-virtual-key-codes-beginning-hotkeys-part-12/ might be helpful for windows - especially if you plan to use AHK to receive special scancodes and act on them. |
May I ask, what is the status of this issue? |
No progress has been made with this issue yet. We don't have an ETA for GitHub issues, and we'll update them when progress is made. |
Will this let me add a handful of emojis? |
No, emojis can be implemented with macros, not with special scancodes. See https://ultimatehackingkeyboard.com/blog/2018/06/23/how-can-i-type-accented-characters-with-my-uhk |
I'd like this quite much. As I've tried to generate a |
I was just looking for Edit - I hit capture and it didn't seem to see that capture that keypress for me. Were you able to make this work @DDzwiedziu? Edit again: Apparently F20 works to send that keycode for me, see this tweet for details |
This feature has been implemented, and it will be included in the next Agent release. |
I've downloaded the latest release but I'm unsure how to input said arbitrary scancode? |
As stated above, entering a code like It might be a good idea to always show custom-scancode entry when custom code is entered - @mondalaci, @ert78gb? Also, custom scancodes could be mentioned in the "?" popover. |
It depends from Laci. I am fine with both solution |
The scancode of B24 and U is the same, and from Agent's standpoint, they're identical. Also, from a usability standpoint, it's better to show the symbolic name of the scancode whenever possible, so we won't change the current behavior. I'll document the custom scancode feature and mention it in the scancode tooltip according to #1642. |
Let's allow users to provide custom scancodes. There are 3 types of scancodes according to the USB interfaces that the UHK exposes:
B
for basic.M
for media.S
for system.As for the valid numeric intervals of the scancodes, it's 1-255 for basic and system scancodes and 1-65535 for media scancodes.
Users will be able to write a string composed of the scancode type and scancode number into the scancode field of the key action popover and the macro editor to specify the desired scancode. Examples are
B62
,M180
, andS10
.The scancode select2 widget won't contain custom scancodes because they're of no use for most. This way, the feature will be available for advanced users, but it won't confuse regular users.
When entering a custom scancode, Agent will look up the scancode.
B62
in the select2 widget, and render its key as such.Currently, Agent replaces unknown scancodes that are not part of the select2 widget with none actions when encountering with them. For this feature to work correctly, Agent must not replace such scancodes anymore, but leave them as they are.
The text was updated successfully, but these errors were encountered: