Dinesh966 / jnativehook

Automatically exported from code.google.com/p/jnativehook
0 stars 0 forks source link

Obtaining scancodes #56

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
It would be useful to obtain scancodes which are completely layout-independent. 
The value is readily available in the kbhook->scanCode field. There only needs 
to be a check if it's less than 0x100 because switching to or from certain 
applications seems to generate WM_KEYUP event scancodes in the range 0x200.

Original issue reported on code.google.com by mark.jeronimus@gmail.com on 22 Jul 2013 at 1:55

GoogleCodeExporter commented 8 years ago
I have been thinking about changing that behavior on windows.  I will see what 
I can do in 1.2.

Original comment by a...@1stleg.com on 22 Jul 2013 at 5:56

GoogleCodeExporter commented 8 years ago
not only windows. Scancodes should be obtainable cross-platform. They are 
keyboard-bound, not OS or locale bound.

Original comment by mark.jeronimus@gmail.com on 23 Jul 2013 at 5:01

GoogleCodeExporter commented 8 years ago
Just for clarification, neither OS X nor X11 provide *ANY* method for accessing 
the scancodes of virtual keycodes reported in userland.  This will be worked 
around using some creative, platform dependent lookups.  Windows should be 
switched over the scancodes at this point in the trunk.  Compilation 
instructions are attached to bug #67.

Original comment by a...@1stleg.com on 9 Sep 2013 at 10:36

GoogleCodeExporter commented 8 years ago
As of 1.2.0-Beta1 Virtual key codes now use scan code set 1 as their values for 
all platforms.

Original comment by a...@1stleg.com on 22 Jan 2014 at 7:42