home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
Installation, configuration support
Configuring a remote - exasperated
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 1157732" data-attributes="member: 82144"><p>Raw keys? Proper MCE-compatible remotes/receivers don't generate key presses, so I can only guess that you're referring to the keyboard shortcut associated with the red button in a specific application (eg. WMC).</p><p></p><p></p><p>I could be wrong, but I think you've misunderstood.</p><p></p><p>CTRL-ALT-1 <em>is </em>an application-specific binding. Attempting to configure each application to recognise a specific keyboard shortcut for each button [and translate that into the action associated with the button - eg. the play button generates CTRL-P, which triggers the play action] is the hard way to do things (if it is even possible).</p><p></p><p>To continue my example, MediaPortal recognises when you press the play button. The <a href="http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/141_Configuration/MediaPortal_Configuration/8_Remote/Mapping_Buttons" target="_blank">mapping </a>configuration is what tells MP what that button means. So for example, the default mapping for the play button is the play action. The fact that MP's keyboard shortcut for play is P is incidental and should be irrelevant when it comes to remote configuration.</p><p></p><p>Another way of thinking about the way MP does things is to realise that you can change the action (meaning) of a button independently of its keyboard shortcut. For example, you could use mapping to make the play button take a screenshot... and this wouldn't change the fact that the keyboard shortcut for the play action would still be P. Similarly you can do the reverse - you can change the keyboard shortcut to SPACE <u>without affecting the function of the remote button</u>.</p><p></p><p>Am I making sense?</p><p></p><p></p><p>Yes, I think you're right.</p><p></p><p></p><p>As above: when you enable the HID handler, it should directly recognise the buttons you're pressing (in technical terms they're called "usages"). The function of the buttons is determined by the mapping you configure. For most people the default mapping is fine for most buttons. The keyboard shortcuts are a separate concern. You shouldn't need to touch them unless you don't like them... and changing them won't affect how your remote functions (unless the remote generates keyboard shortcuts, which is a bad thing!).</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1157732, member: 82144"] Raw keys? Proper MCE-compatible remotes/receivers don't generate key presses, so I can only guess that you're referring to the keyboard shortcut associated with the red button in a specific application (eg. WMC). I could be wrong, but I think you've misunderstood. CTRL-ALT-1 [I]is [/I]an application-specific binding. Attempting to configure each application to recognise a specific keyboard shortcut for each button [and translate that into the action associated with the button - eg. the play button generates CTRL-P, which triggers the play action] is the hard way to do things (if it is even possible). To continue my example, MediaPortal recognises when you press the play button. The [URL='http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/141_Configuration/MediaPortal_Configuration/8_Remote/Mapping_Buttons']mapping [/URL]configuration is what tells MP what that button means. So for example, the default mapping for the play button is the play action. The fact that MP's keyboard shortcut for play is P is incidental and should be irrelevant when it comes to remote configuration. Another way of thinking about the way MP does things is to realise that you can change the action (meaning) of a button independently of its keyboard shortcut. For example, you could use mapping to make the play button take a screenshot... and this wouldn't change the fact that the keyboard shortcut for the play action would still be P. Similarly you can do the reverse - you can change the keyboard shortcut to SPACE [U]without affecting the function of the remote button[/U]. Am I making sense? Yes, I think you're right. As above: when you enable the HID handler, it should directly recognise the buttons you're pressing (in technical terms they're called "usages"). The function of the buttons is determined by the mapping you configure. For most people the default mapping is fine for most buttons. The keyboard shortcuts are a separate concern. You shouldn't need to touch them unless you don't like them... and changing them won't affect how your remote functions (unless the remote generates keyboard shortcuts, which is a bad thing!). [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Installation, configuration support
Configuring a remote - exasperated
Contact us
RSS
Top
Bottom