I'm finding the documentation around the Mythtv lirc mapping (lirc codes to Myth codes) lacks clarity around things like how the entries in 'lircrc' (mythtv) are interpreted and mapped once Myth fires up.
I'd like to fix this up a bit as I've been grinding away on MythTV across CentOS, SuSE and Ubuntu - close to having it ready for my spouse approved deployment to our living room. Finalizing the remote bindings is my last hurdle..
So, before I start walking the code (focused on ./mythtv/libs/libmythui/lirc*) to figure stuff out, I thought I would ask the larger forum. (If anyone knows a thread that answer my query, please let me know! My searching has not found concrete results.)
In the MythTV 'lircrc' file, how are the different (MYSQL table) 'keybindings' mapped up, and in particular to a specific 'context'?
The core issue is:
- lirc configured to generate the lirc command KEY_STOP
- The need for KEY_STOP to have two separate behaviors depending on the MythTV context.
- Because the one MythTV keyboard binding is already in use in both contexts.
Something that, in effect does the following:
begin
prog = mythtv
context = Music
remote = mceusb
button = KEY_STOP
config = O
end
begin
prog = mythtv
context = TV Playback
remote = mceusb
button = KEY_STOP
config = Esc
end
TIA!