2013-06-15, 19:13
Given my pain with remote controls in an earlier thread (and the way in which IR has changed which may have left many guides deprecated/inaccurate), something that shows which remote keypresses have been detected by XBMC should illustrate if hardware at both ends are speaking the same language.
I know from earlier experiences the messages sent from the remote didn't match what XBMC were expecting. I used the "irw" command to overhear what the controller was mumbling, then used those responses as triggers for my desired actions.
When enabled, I'd envisage this as being a small notification (bottom-left?) that just showed a scrolling window of the last 3-5 keypresses. This could be part of the debug mode, but would mean people less confident in Linux could enable/disable the option from the GUI.
(I'm hoping this could drive the development of some graphical tool to help binding custom keypresses to additional functionality, similar to how keymapping configuration is performed in games)
I know from earlier experiences the messages sent from the remote didn't match what XBMC were expecting. I used the "irw" command to overhear what the controller was mumbling, then used those responses as triggers for my desired actions.
When enabled, I'd envisage this as being a small notification (bottom-left?) that just showed a scrolling window of the last 3-5 keypresses. This could be part of the debug mode, but would mean people less confident in Linux could enable/disable the option from the GUI.
(I'm hoping this could drive the development of some graphical tool to help binding custom keypresses to additional functionality, similar to how keymapping configuration is performed in games)
