Make Enter bring up full TV guide? (2 Viewers)

[mm1352000]

(7) Enhancements that could be considered: if the "Sceneo tab/Centarea HID" works for all keyboard-shortcut remotes, perhaps it should be renamed, to make its general applicability clearer? If it does not work for all keyboard-shortcut remotes, perhaps a new tab should be added?

Yes, those are pretty much the same thoughts I'm having.

Thinking about this now, I probably ought to try my Ortek using the built-in definition for "Centarea HID", to see if that actually works without using the Ortek config file. I will try that tomorrow and report back.

Looking forward to your results.

 

[Stéphane Lenclud]

Did not read the whole thing there and I have limited knowledge of the various remote handler implementations.

What I do know is that MP1 needs to unify it's input handling. I think both keyboard and remote input should be handled much the same way.

Then we also need input profiles. Say a MP classic profile, a WMC profile, a new MP profile if we wanted to. Then users should be able to create their own profiles too.

Users with those funny remotes that emulate WMC shortcuts could just use the WMC input profile and be done with it.

 

[mm1352000]

What I do know is that MP1 needs to unify it's input handling. I think both keyboard and remote input should be handled much the same way.

I don't understand what you mean by this.

Then we also need input profiles. Say a MP classic profile, a WMC profile, a new MP profile if we wanted to. Then users should be able to create their own profiles too.

If by profile you mean a set of keyboard shortcut assignments (ie. keymap.xml) then I guess I could agree this might be useful for people who prefer to assign alternative keyboard shortcuts and/or people who have remotes which generate hard-coded keyboard shortcuts. Surely this would make no difference for the people who exclusively use remotes which don't generate keyboard shortcuts (ie. the vast majority of people).

 

[Stéphane Lenclud]

I don't understand what you mean by this.

Well keyboards and mice are HID devices. Instead of using the higher level handlers we could handle those input through our HID handler. At least for keyboards anyway.

ATM we have specific code path for keyboards and remotes that should not be needed. We could get ride of keymap.xml and have a single XML file to map any key input to MP actions, be it a keyboard key or a remote key.

That's would also help fixing AZERTY digit handling too.

 

[Stéphane Lenclud]

I don't understand what you mean by this.

Well keyboards and mice are HID devices. Instead of using the higher level handlers we could handle those input through our HID handler. At least for keyboards anyway.

ATM we have specific code path for keyboards and remotes that should not be needed. We could get ride of keymap.xml and have a single XML file to map any key input to MP actions, be it a keyboard key or a remote key.

That's would also help fixing AZERTY digit handling too.

 

[Stéphane Lenclud]

If by profile you mean a set of keyboard shortcut assignments (ie. keymap.xml) then I guess I could agree this might be useful for people who prefer to assign alternative keyboard shortcuts and/or people who have remotes which generate hard-coded keyboard shortcuts. Surely this would make no difference for the people who exclusively use remotes which don't generate keyboard shortcuts (ie. the vast majority of people).

HID remotes could have profiles too. Once input handling is unified it is one and the same.

 

[mm1352000]

Well keyboards and mice are HID devices. Instead of using the higher level handlers we could handle those input through our HID handler. At least for keyboards anyway.

My understanding is that some remotes, keyboards and/or related programs generate/inject key press events without going through the HID layer. If I'm right and we did as you're suggesting, it would not be possible to receive input from those sources.

 

[Stéphane Lenclud]

My understanding is that some remotes, keyboards and/or related programs generate/inject key press events without going through the HID layer. If I'm right and we did as you're suggesting, it would not be possible to receive input from those sources.

Only dodgy software do that
SoundGraph iMON for instance.
Implementation would need to be backward compatible anyway.

 

[mm1352000]

LOL
Unfortunately people who use MediaPortal will expect us to support all hardware and software, regardless of how dodgy it is.
Anyhow, there'd be no harm in trying such a rework.