[mythtv] Some ideas about mythtv and input devices

[Keith Layne]

Well, lircrc is kind of a pain by itself, but I was actually referring to
managing it through the frontend.  The lirc source probably has lex/yacc
files for the config (I hope), but if you use lirc for anything else (xine
for example) you would have to make sure that you didn't squash those
entries.  Plus you don't want to kill comments etc.  

I guess it's an advantage that the keybindings are stored in the db (I
assume this is true, anyway).  I read somewhere in some setup instructions
that it's a good idea to link ~/.lircrc to ~/.mythtv/lircrc.  I did that,
got lirc working, and promptly accidentally wrote over everything while
configuring lirc support for xine.  Admittedly, I'm an idiot sometimes, but
that's the kind of thing that we should be able to avoid.  The lirc
interface lets you specify a config file...what does anyone thing about
building a lircrc on the fly from the db and feeding that to the lirc
interface?  It might certainly make some things easier, and follow the model
of the keybindings.  This could all fall under mythcontrol.

Thoughts?

Keith


-----Original Message-----
From: mythtv-dev-bounces at mythtv.org [mailto:mythtv-dev-bounces at mythtv.org]
On Behalf Of Colin Guthrie
Sent: Wednesday, December 27, 2006 7:40 AM
To: Development of mythtv
Subject: Re: [mythtv] Some ideas about mythtv and input devices

Hi,

Keith Layne wrote:
> Of course, for lirc specifically there are some issues, like dealing
> with the clunky config file.  Also, it looks like the lirc client is
> just spun off into a thread.  It would be nice to add the ability to
> easily kill this one off and start a new one, so that changes to remote
> configs could be effected without restarting the frontend.

While being a bit of a nerd and not really midning playing with,
admittedly, clunky LIRC configs, I'd certainly support the ability to
restart lirc or reconnect to the socket etc.

One of the problems I had when my LIRC actually worked (the h/w broke
ages ago and I'm too lazy to fix it), was resuming from suspend. The
Remote would not work unless I quit and reloaded the frontend. Which
isn't too nice all in all.

Could be I missed something or some tweak/hack that would have made it
work... I'm gonna invest in a new frontend machine soon anyway. It wants
to be diskless and 100% silent (pref completely passivly cooled). Any
suggestions people want to throw at me please feel free (tho' I
appreciate this is a -user question, I'm just being lazy - hey it's the
holidays after all!)

Col.

-- 

+------------------------+
|     Colin Guthrie      |
+------------------------+
| myth(at)colin.guthr.ie |
| http://colin.guthr.ie/ |
+------------------------+
_______________________________________________
mythtv-dev mailing list
mythtv-dev at mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev