[mythtv] Question regarding LIRC support and gContext->getCurrentLocation()

Navaho Gunleg navahogunleg at gmail.com
Tue May 30 13:40:01 UTC 2006

On 5/30/06, Stuart Morgan <stuart at tase.co.uk> wrote:
> On Tuesday 30 May 2006 13:43, Navaho Gunleg wrote:
> > > So just rebind the keys. E.G. Bind D in the Teletext Menu context to
> > > whatever action you want and to Delete in the other contexts.
> >
> > Well, that's just it. As I mentioned, remapping would indeed solve it,
> > but I do not want to touch the default key-assignments -- these work
> > fine for me when I /do/ use the keyboard.
> Sorry didn't actually read that far.
> I'd suggest that if changes were made to the lirc support that it would be a
> good idea to map directly to Myth actions instead of keys. It's been
> discussed in the past, I didn't pay much attention at the time but I seem to
> recall some resistance to that idea. Still it would allow both  keyboard and
> remote to be configured differently without a making lirc configuration too
> complicated. It would even be easier to code (he says without actually
> looking at the current stuff).
> It would also be nice to see remote key config brought under Myth's own UI,
> much like MythControls allows now for keyboard config.
> I'm not suggesting that you do both these things, I'm just raising them for
> discussion. I might even do it myself when I've finished my other tasks.

Indeed -- I have also been pondering 'native' LIRC support -- but not
using the lirc client libraries, but like the 'irw' utility does,
using the LIRC socket. This would require *major* modifications and,
at the moment, my understanding of both LIRC and especially such a big
project as MythTV just isn't good enough to accomplish this. The other
hack was pretty straight-forward really.

Complete integration would be the /most/ elegant solution; imagine
MythControls itself accepting the "Menu/i", "Play", "SkipForward"
identifiers from the LIRC socket. That would really be awesome. ;)

All in all, LIRC support, in its current form, is pretty basic and
extending its support throughout all of MythTV seems only a logical
next step. I don't use a joystick, but noticing the joystick thread
getting spawned in a similar way, I am assuming that those assignments
don't have any 'context' either so to speak? It could be wise to take
those into account as well.

Just thinking out loud.

More information about the mythtv-dev mailing list