Re: Linux input event generation using uinput

[<li...@ba...>]

Hi!

Juan Jesús García de Soria Lucena "ska...@gm..." wrote:
> I had to patch the input_map.sh script (patch attached), since it
> wasn't working and I got an empty namespace. I had to manually fix the
> generated .inc file, since it was choking on a multi-line comment (it
> would copy only the "/*" part, leaving the some of the following list
> entries commented).

Can you send me the input.h that gives problems?

[...]
> Autorepeat was triggering in too early, no matter how I configured
> GNOME keyboard properties. I've seen the code in lircd.c, and I reckon
> it's trying to use the auto-repeat support in the input layer.

During implementation I found that the input layer behaves not very  
intuitive here.

>
> I've tried to change it so that it works better for me. Most
> experiments ended up with autorepeat going on even after I had
> released the remote key. The only behaviour I find reasonable is when
> I do the following:
>
> 1. Define an auto-repeat threshold T (T=0 disabled).
>
> 2. For the first press (reps = 0), emit a press (event.value = 1) and
> a release (event.value = 0) in succession.
>
> 3. If auto-repeat is enabled, for each press with reps >= T, emit a
> repeat-press (event.value = 2) and a release (event.value = 0) in
> succession.

I wonder if there is a "correct" way to use auto-repeat.

Christoph