No keyText
Closed this issue · 11 comments
No keyText.
These keys, and probably a lot more, return keyText "Undefined"
VK_SLEEP vkCode=0x05F
VK_LAUNCH_APP1 vkCode=0x0B6
VK_VOLUME_MUTE vkCode=0x0AD
VK_VOLUME_DOWN vkCode=0x0AE
VK_VOLUME_UP vkCode=0x0AF
Original issue reported on code.google.com by mark.jeronimus@gmail.com on 23 Jul 2013 at 5:43
- Blocked on: #59
Original comment by a...@1stleg.com on 9 Sep 2013 at 10:38
- Changed state: Accepted
- Now blocked on: #59
Original comment by a...@1stleg.com on 17 Apr 2014 at 6:16
- Changed state: Started
Issue 61 has been merged into this issue.
Original comment by a...@1stleg.com on 17 Apr 2014 at 6:17
This should be resolved in 1.2.0-Beta2 with the exception of VK_LAUNCH_APP1 and
VK_LAUNCH_APP2. If you can get me the scancode value for that key I can add
it. Just re-open this ticket.
Thanks!
Original comment by a...@1stleg.com on 17 Apr 2014 at 8:28
- Changed state: Fixed
VK_LAUNCH_APP2 is commonly the "Calculator" button with scancode 121 and
keycode 0B7
Original comment by mark.jeronimus@gmail.com on 18 Apr 2014 at 8:29
I gathered some scancodes and keycodes here:
https://docs.google.com/spreadsheet/ccc?key=0AhGVXv8PGuHadDRKVW1uQkZKQ1JLRWVmUjZ
6anFNVVE&usp=sharing
Original comment by mark.jeronimus@gmail.com on 18 Apr 2014 at 8:30
Looks like none of the extended keys are producing scancodes on Windows and I
am not sure why. For example pressing the calculator app2 button seems to
report a scancode of 0x00 with a 0x11 flag!? When using JNativeHook do all
scancodes for extended buttons appear as 0xE00 for you? How are you able to
capture scancodes for these keys?
Original comment by a...@1stleg.com on 19 Apr 2014 at 4:14
- Changed state: Accepted
I don't know why it returns 0. It also does so in my own LowLevelKeyboardProc
hook application. However, knowing it runs on windows, you can map every vkCode
back to a scancode with a look-up table.
Original comment by mark.jeronimus@gmail.com on 20 Apr 2014 at 9:33
I am going to push this bug back to after beta2. The lookup table would be a
faster solution, its just going to be tricky with the bi-directional
requirement.
Original comment by a...@1stleg.com on 21 Apr 2014 at 3:08
This should be pretty close to complete in the trunk. I will be posting RC1 in
the coming week.
Original comment by a...@1stleg.com on 16 Jun 2014 at 6:20
- Changed state: Started
This should be fixed in the trunk. RC1 will be up shortly.
Original comment by a...@1stleg.com on 30 Aug 2014 at 12:40
- Changed state: Fixed