Hi!

Joe Flint <[EMAIL PROTECTED]> wrote:
> The current code is assuming that if pylirc.nextcode() returns an
> empty list, then it means that the previous button was repeated. This
> is indeed what happens, but I think it could be handled a better way.
> LIRC supports a repeat parameter in lircrc files that allows a button
> to repeat. Pylirc seems to support this (I have 0.0.4) and sends the
> name of the button in the list every time (if repeat=1 in lircrc),
> instead of just an empty list.

Yes, I noticed the same behaviour and found a bug in pylirc which was
fixed on 2005-01-06 in pylirc 0.0.5. The new version is still
compatible with freevo 1.5.x and 2.x but it does handle now "repeat"
and "delay" keywords in .lircrc correctly and does not generate events
for other remotes or unspecified remote keys.
Give it a try, it's wonderful! :-)

 Sönke
-- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it."  (Brian W. Kernighan)

Attachment: signature.gpg
Description: Dies ist eine PGP/GPG-Signatur. This is a PGP/GPG signature.

Reply via email to