| Ticket UUID: | c32f86d43dad6ff4929cdbcf0dbf5d30793ca910 | |||
| Title: | Discriminate between numpad and numeric row for voice channel hotkeys | |||
| Status: | Open | Type: | Feature_Request | |
| Severity: | Minor | Priority: | Low | |
| Subsystem: | Windows | Resolution: | Open | |
| Last Modified: | 2019-06-17 22:20:56 | |||
| Version Found In: | where do you find this lol | |||
|
TA10S — 2019-06-16 22:02:01 If I bind a button to the numpad (say, 0) it saves it as if it were on the top number row. Happens with all numpad buttons. (Not sure if this is a bug or not) | ||||
|
cancel — 2019-06-17 22:17:49 This is for voice chat hotkeys. This is a limitation of the RegisterHotKey API, I think. I'll take a look at it later. I may end up having to use RawInput on Windows due to the RegisterHotKey limitations. But I'm trying to avoid using RawInput because it's invasive (it's the kind of hook you'd use to write a keylogger...) | ||||