[mythtv] [mythtv-commits] Ticket #6315: LIRC Keypresses sent to both mythwelcome and mythfrontend
Michael T. Dean
mtdean at thirdcontact.com
Thu Mar 26 00:53:15 UTC 2009
On 03/25/2009 02:47 PM, MythTV wrote:
> #6315: LIRC Keypresses sent to both mythwelcome and mythfrontend
>
>
> Comment(by Matthew Wire):
>
> Seems it's not quite fine...
> I've just found out why I originally put the "&" in there. If
> mythfrontend is allowed to block it also blocks irexec from working (I
> have a number of external scripts for power on/off and volume control of
> my amp). irexec command line is ''irexec -d /home/mythtv/.lircrc''.
That can't happen. The way LIRC works, it sends a message to /all/
listeners on the socket (generally /dev/lircd) that contains some info:
<code> <repeat count> <button name> <remote control name>
and it's up to the application to "do the right thing" based on the
configuration specified in the LIRC config (~/.lircrc or, for Myth,
~/.mythtv/lircrc, if it exists). Therefore, button press messages are
/always/ broadcast to all clients. TTBOMK, there's nothing that Myth
can do to block the communications on the socket. Instead, Myth simply
reacts to those buttons for which the .lircrc specifies a config for the
program mythtv--unless Myth is "ignoring" LIRC button presses (i.e.
after spawing an external app, such as xine or mplayer or ... until that
app terminates) and does nothing when receiving a button press for a
button not configured for program mythtv.
See http://lirc.org/html/technical.html#applications .
I'm pretty sure something else is preventing your irexec from
working--unfortunately, I don't know what that could be.
Mike
More information about the mythtv-dev
mailing list