Hello Brett,
Lircd listens to a sensor through a kernel module. What comes from the
sensor is a code, something like "0x40BF20DF", which you can pair with a
label, like "DOWN" and a remote name, like "Avermedia".
What I'm trying to say is that the remote config property is just a logical
value. What's really important is the code, and there is no way lirc could
tell that the same code belongs to a remote in some cases and to another in
other cases.
On Feb 18, 2008 9:07 PM, Brett Granger <[EMAIL PROTECTED]> wrote:
> The "key lock" functionality may be useful as well, but I wonder if it
> is possible to prevent your TV remote from interfering with freevo by
> using the "remote=" capabilities of lircrc? I don't know the details,
> but I know it is possible to limit which keys go to which programs based
> on the type of remote. If lirc can tell whether it's your TV remote
> sending the keys or the "freevo" remote, then you wouldn't need to lock
> the keys at all... What I don't know is whether all remote keys that
> come in through the same IR sensor are considered the "same remote" or
> if it's possible for lirc to tell that two different remotes are using
> the same sensor?
>
> Check out the "The .lircrc file format" section of
> http://www.lirc.org/html/configure.html
>
> --Brett
>
> José María Franco Fraiz wrote:
> > Hello to everyone:
> >
> > I recently got myself a new TV set to find out that the new tv remote
> > control interacted with the ir sensor I have in my freevo box. After
> > trying a lot of things in order to avoid this side-effect I decided to
> > make a change in freevo itself, and I think it could be useful for other
> > people. It's something like a remote key lock/unlock feature.
> >
> > When the remote is locked no remote key is processed, until it's
> unlocked.
> >
> > Here is the patch (I might have done the patch wrong, it's the first
> > time I make one, so please fix it if it's wrong).
> >
> > --------------------------
> >
> > --- rc.py 2008-02-17 13:24:41.000000000 +0100
> > +++ rc.py 2007-11-18 20:49:50.000000000 +0100
> > @@ -179,8 +179,6 @@
> > self.default_keystroke_delay1 = 0.25 # Config
> > self.default_keystroke_delay2 = 0.25 # Config
> >
> > - self.keylock = False
> > -
> > global PYLIRC
> > PYLIRC = True
> >
> > @@ -265,14 +263,8 @@
> > self.lastkeystroke = nowtime
> > self.repeat_count += 1
> >
> > - for code in list:
> > - if code == config.KEYLOCK and not(self.keylock):
> > - self.keylock = True
> > - if code == config.KEYUNLOCK and self.keylock:
> > - self.keylock = False
> > - print self.keylock
> > - if self.keylock == False:
> > - return code
> > + for code in list:
> > + return code
> >
> >
> > #
> >
> --------------------------------------------------------------------------------
> > @@ -471,7 +463,6 @@
> > self.inputs = []
> > if use_pylirc:
> > try:
> > -
> > self.inputs.append(Lirc())
> > except:
> > pass
> >
> > -------------
> >
> > It uses two config variables in the local_conf.py (key labels in
> lircrc):
> > KEYLOCK = 'INPUT'
> > KEYUNLOCK = 'Q.VIEW'
> >
> > It would be very nice to have some visual feed back, something like a
> > little icon in the idle bar that shows when the remote is locked and
> > unlocked, but that goes far beyond my knowledge of freevo / python.
> > Perhaps someone with more experience could add this functionality.
> >
> > Greetings
> >
> >
> > ------------------------------------------------------------------------
> >
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Freevo-devel mailing list
> > Freevo-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/freevo-devel
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Freevo-devel mailing list
> Freevo-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freevo-devel
>
--
José María Franco Fraiz
Altia Consultores
Colón, 28 3º. 36201 Vigo
Telef: +34 986 446 191 Ext. 20
Fax: +34 986 439 128
Este documento se dirige exclusivamente a su destinatario por poder contener
información confidencial o cuya divulgación deba estar autorizada en virtud
de la legislación vigente. Se informa a quien lo recibiera sin ser el
destinatario o persona autorizada por éste, que la información contenida en
el mismo es reservada y su utilización o divulgación con cualquier fin está
prohibida. Si ha recibido este documento por error, le rogamos que nos lo
comunique por esta misma vía o por teléfono (981-138847, 986-446191,
945-121939, 981-569773) y proceda a su destrucción.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Freevo-devel mailing list
Freevo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-devel
