daltonfury42 / logkeys

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

Support laptop Function (Fn) key #58

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
(This is an enhancement request.)

Many laptops feature a specific key named Function situation near the Control, 
Alt, or OS key (Windows, Command, etc). I would like logkeys to identify for 
debugging purposes when this key is pressed similar to how it regards Shift, 
Ctrl or Alt.

logkeys 0.1.1a
Ubuntu 10.10 i386

When I press the Function key ONE time on my keyboard followed by <Enter>, I 
get the following output in the log file. Notice, I pressed Ctrl-C to exit.

2011-05-17 06:01:30+0000 > 
<E-1d0><E-1d0>
2011-05-17 06:01:32+0000 > <LCtrl>^C

Thanks

Original issue reported on code.google.com by byu...@gmail.com on 17 May 2011 at 6:03

Attachments:

GoogleCodeExporter commented 9 years ago
I knew I tested this before...

You see, this doesn't appear to work evenly on all configurations.
On my, for example, pressing Fn alone produces no notice, while pressing Fn+M 
produces
<KP0> (that's keypad 0) on my keypad-less laptop (with keypad superimposed on 
the upper right of alphabet keyboard).
Fn+Enter produces <KP_Enter>, which for our use acts the same (produces a new 
line in the log file). If I first press Fn once followed by Enter, it's the 
same.

According to /usr/include/linux/input.h, 0x1d0 (correctly) corresponds to
#define  KEY_FN  0x1d0
but for reason mentioned (doesn't work for me), I don't look for that key (or 
any above 0x7f).

What OS are you on? What laptop?
Our dumpkeys outputs match, so this must be on a lower level (either kernel or 
hardware).

Original comment by kernc...@gmail.com on 17 May 2011 at 8:29

GoogleCodeExporter commented 9 years ago
The laptop is an Acer Aspire Timeline 5810T.
I was using a Ubuntu 10.10 i386 live CD when I submitted the details above.

Also under the current Ubuntu 11.04, pressing the Function key along with Left 
and Right arrow will crash X desktop, so I was interested in using logkeys to 
examine what keystrokes are being generated.

Thank you.

Original comment by byu...@gmail.com on 24 May 2011 at 11:13