Re: problem with multiple devinput keys

[Yan S. <ya...@se...>]

Christoph Bartelmus wrote:
> Hi!
>
> Yan Seiner "ya...@se..." wrote:
>   
>> I got a cheap USB IR remote that emulates a keyboard.  On some keys it
>> sends out several characters.  The problem is that these are seen as
>> multiple button pushes, even if I have flags = quit set...
>>     
> [...]
>   
>> output from irexec - for some reason, the A and 1 keys are seen as
>> separate key strokes AND the whole FA pattern is also seen - in spite of
>> using the quit flag....  But this doesn't happen with the NoClue key.
>>     
>
> What do you expect to happen?
> The quit flag is only evaluated at the end of the sequence.
> It works for the NoClue key because the sequence ends with Tab.
> The FA sequence ends with F1, not with A or 1.
>
> If you want only A and 1 to be executed, you have to place them before the  
> FA sequence, but then FA never will be executed.
>
> It's not a bug, it's a "feature".
>
>   
OK, I got if figured out.... It's a feature....

The parser doesn't keep track of where it is.  What's needed to get the 
functionality I want is:

1.  Loop through lircrc scanning for key.  If it's found, set a flag 
that says we're in mid-pattern.  Check if pattern is complete..
2.  If pattern is complete, output pattern and clear flag.
3.  If pattern is not complete, remember our position in the pattern and 
get next character.
4.  If we can't find a matching pattern and we've exhausted all 
patterns, clear flag and reject pattern.

This is very similar to how a VT100 or ANSI terminal emulator works.  I 
have the code for one that I wrote somewhere....

Is this a useful addition to lirc?  It would allow complex code patterns 
to be interpreted "correctly".

--Yan