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

Navaho Gunleg navahogunleg at gmail.com
Tue May 30 15:54:22 UTC 2006

On 5/30/06, Michael T. Dean <mtdean at thirdcontact.com> wrote:
> On 05/30/2006 09:40 AM, Navaho Gunleg wrote:
> > On 5/30/06, Stuart Morgan <stuart at tase.co.uk> wrote:
> >
> >> 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.
> I agree, but IMHO, it makes sense only if the mapping is done within
> Myth, not within LIRC.  I.e. we link the LIRC identifier string
> (whatever string is specified for the button in the ~/.mythtv/lircrc
> file) to the Myth action.  Many have suggested the opposite
> approach--specifying Myth action names in the lircrc file.  I don't
> think any remote has that many buttons and we shouldn't be specifying
> Myth contexts in the lircrc file.

Well -- in my case it was the actual lack buttons that made me hack
this quick and dirty solution in and made me think about this some
more -- but I definitely do see the point you make.

Caught in a line of thought I didn't even think of it the opposite
way. In fact, that approach would require even less modifications to
all the code and I can definitely see the ease of configuring things.

Yeah, I definitely dig your suggestion.

This could just be made possibly as easy as a slight alteration to the
LircKeycodeEvent to store the lircrc configured token, and the
customEvent-handler to act upon it. Hmm, as I type this, a quick peek
into the customEvent( ) handler tells me that getting, say, the "Red"
token into the key-press handler could be a problem though. But I sure
could be missing something. :)


More information about the mythtv-dev mailing list