Lirc and long keypresses.

[Mark DM <mar...@gm...>]

I see that there seems to be some issues with getting LIRC to
recognize long keypresses , however this seems to also baffle me as to
why .  see http://forum.xbmc.org/showthread.php?tid=115023

I have a Creative Labs Sound Blaster Audigy 2 NX . I only use the IR
functionality.

When I launch irw and hit a key I see this
000000000000001f 00 ok RM-1500
with "ok" corresponding to the key pressed.

Now with irw if I press and hold a key for about 3 seconds I see this
000000000000001f 00 ok RM-1500
000000000000001f 01 ok RM-1500
000000000000001f 02 ok RM-1500
000000000000001f 03 ok RM-1500
000000000000001f 04 ok RM-1500
000000000000001f 05 ok RM-1500
000000000000001f 06 ok RM-1500
000000000000001f 07 ok RM-1500
000000000000001f 08 ok RM-1500
000000000000001f 09 ok RM-1500
000000000000001f 0a ok RM-1500
000000000000001f 0b ok RM-1500
Clearly the entry before "ok" corresponds to the time the button was pressed.

My question is therefore very simple.....

Since we can now use simply "ok" to identify that the "ok" button was
pressed, why can we not identify a duration by saying instead of "ok"
we say , "0b ok" meaning a three second button press would yield a
specific behavior? I see no issue in making this an option ,
especially when the button does not conflict with another use. An
example would be when XBMC is not running and I want to long press
"ok" or "0b ok" to start XBMC, but that does not mean I want to launch
XBMC when the remote falls on the floor and that button gets pressed,
or when the cat steps on it while chasing a fly. In fact it coul;d
probably be implemented while leaving compatibility with older
configuration files as only those needing long keypresses would
require the additional "0b"

I understand that the idea above is not what they were looking for in
the apple thread, but a step in the right direction.

As I recall the apple remote seems to have a very fast repeat rate,
and maybe much faster than my creative remote and in relation to the
apple thread if the repeat rate was twice the rate of the creative
well 1/8 of a second is not too much of a lag to wait to see if there
is a long keypress or not. Also recognizing that only certain buttons
would have dual function for long or short press this lag would not
even have to apply to all buttons

Maybe there is something I am missing and it can already be done?

Just my two cents from someone trying to use this stuff!

 Mark