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
Input / Output interfaces
Remotes
MP 1.23 Key Mapping
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="macmr" data-source="post: 1265739" data-attributes="member: 115062"><p>And what does this mean?</p><p></p><p>Anyway getting back to CyberSimian's thoughtfull and concise response.</p><p></p><p>No I don't think that you are giving me the brush off. Far from it I respect your honesty in explaining the problems with the lack of developers especially some of the original guys who made MP what it is today. I do realise that it is very difficult to take over someone elses coding and be able to make sense of their thought patterns. As you say this may be a bug but from the sound of it it will never get fixed.</p><p></p><p>Is it still worth logging a bug report or is it in the too hard basket?</p><p></p><p>As mentioned in an earlier post this problem affects the HID handler of at least MP 1.23 and probably some recent versions. Some people may never even have a problem depending on what HID codes their remotes are using.</p><p></p><p>Ok my final and cleanest fix (I hope) for anyone that may have the same problems as I had.</p><p></p><p>I am now running the original key map files as delivered in the MP 1.23 package. I have not enabled any of the options in the Remotes & Input Devices section in Mediaportal Configuration setup. I copied my MP 1.14 KeyboardInputPlugin.dll file into the Program Files\Team MediaPortal\MediaPortal\plugins\process directory and the keyboard.xml file (the mapping file for the plugin) into ProgramData\Team MediaPortal\MediaPortal\InputDeviceMappings. This now makes the plugin show up in the plugins section of the Configuration setup and allows key remapping.</p><p></p><p>This copying was necessary because the KeyboardInputPlugin is no longer available even though it shows as being downloadable in the extensions manager?</p><p></p><p>I realise that as this plugin is no longer available it won't help anyone that can't get it from somewhere but that is my fix none the less.</p></blockquote><p></p>
[QUOTE="macmr, post: 1265739, member: 115062"] And what does this mean? Anyway getting back to CyberSimian's thoughtfull and concise response. No I don't think that you are giving me the brush off. Far from it I respect your honesty in explaining the problems with the lack of developers especially some of the original guys who made MP what it is today. I do realise that it is very difficult to take over someone elses coding and be able to make sense of their thought patterns. As you say this may be a bug but from the sound of it it will never get fixed. Is it still worth logging a bug report or is it in the too hard basket? As mentioned in an earlier post this problem affects the HID handler of at least MP 1.23 and probably some recent versions. Some people may never even have a problem depending on what HID codes their remotes are using. Ok my final and cleanest fix (I hope) for anyone that may have the same problems as I had. I am now running the original key map files as delivered in the MP 1.23 package. I have not enabled any of the options in the Remotes & Input Devices section in Mediaportal Configuration setup. I copied my MP 1.14 KeyboardInputPlugin.dll file into the Program Files\Team MediaPortal\MediaPortal\plugins\process directory and the keyboard.xml file (the mapping file for the plugin) into ProgramData\Team MediaPortal\MediaPortal\InputDeviceMappings. This now makes the plugin show up in the plugins section of the Configuration setup and allows key remapping. This copying was necessary because the KeyboardInputPlugin is no longer available even though it shows as being downloadable in the extensions manager? I realise that as this plugin is no longer available it won't help anyone that can't get it from somewhere but that is my fix none the less. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Input / Output interfaces
Remotes
MP 1.23 Key Mapping
Contact us
RSS
Top
Bottom