Reply to thread

Message

Hi Johan, the plugin re-uses the existing MediaPortal remote button/input mapping mechanism which AFAIK doesn't support the functionality that you requested. Currently I do not have plans to replace the MediaPortal input mechanism with my own version, so unless somebody else implements this (either in MediaPortal itself or in the KeyboardInputPlugin) this functionality will not be supported in the near future.

There is a workaround though; add the button and map it to some arbitrary window, and then manually change the keyboard.xml file. For the given button mapping you will have to modify the value of the cmdproperty attribute to the window/plugin-id of your choice (the window id can be found by looking at the source of the plugin) . Be wary though; your keyboard.xml configuration file will be deleted when you press the 'Update Mapping' button in the KeyboardInputPlugin configuration after making such changes, as the MediaPortal input mapping mechanism doesn't understand this.

So the correct workaround would be to create all mappings that you want using the setup screens, as far as possible. Then make a backup (1) of your InputDeviceMappings\custom\keyboard.xml file, then manually change any mappings that you want, and make a backup (2) of that file again. Should you ever want to modify the mapping again using the setup program, replace the InputDeviceMappings\custom\keyboard.xml file with backup (1), make your changes, and re-apply all manual changes again.

Kind regards,
Ruud.

<blockquote data-quote="rsenden" data-source="post: 172766" data-attributes="member: 24295">Hi Johan, the plugin re-uses the existing MediaPortal remote button/input mapping mechanism which AFAIK doesn't support the functionality that you requested. Currently I do not have plans to replace the MediaPortal input mechanism with my own version, so unless somebody else implements this (either in MediaPortal itself or in the KeyboardInputPlugin) this functionality will not be supported in the near future.There is a workaround though; add the button and map it to some arbitrary window, and then manually change the keyboard.xml file. For the given button mapping you will have to modify the value of the cmdproperty attribute to the window/plugin-id of your choice (the window id can be found by looking at the source of the plugin) . Be wary though; your keyboard.xml configuration file will be deleted when you press the 'Update Mapping' button in the KeyboardInputPlugin configuration after making such changes, as the MediaPortal input mapping mechanism doesn't understand this.So the correct workaround would be to create all mappings that you want using the setup screens, as far as possible. Then make a backup (1) of your InputDeviceMappings\custom\keyboard.xml file, then manually change any mappings that you want, and make a backup (2) of that file again. Should you ever want to modify the mapping again using the setup program, replace the InputDeviceMappings\custom\keyboard.xml file with backup (1), make your changes, and re-apply all manual changes again.Kind regards,Ruud.</blockquote>

[QUOTE="rsenden, post: 172766, member: 24295"] Hi Johan, the plugin re-uses the existing MediaPortal remote button/input mapping mechanism which AFAIK doesn't support the functionality that you requested. Currently I do not have plans to replace the MediaPortal input mechanism with my own version, so unless somebody else implements this (either in MediaPortal itself or in the KeyboardInputPlugin) this functionality will not be supported in the near future. There is a workaround though; add the button and map it to some arbitrary window, and then manually change the keyboard.xml file. For the given button mapping you will have to modify the value of the cmdproperty attribute to the window/plugin-id of your choice (the window id can be found by looking at the source of the plugin) . [COLOR="Red"]Be wary though; your keyboard.xml configuration file will be deleted when you press the 'Update Mapping' button in the KeyboardInputPlugin configuration after making such changes, as the MediaPortal input mapping mechanism doesn't understand this.[/COLOR] So the correct workaround would be to create all mappings that you want using the setup screens, as far as possible. Then make a backup (1) of your InputDeviceMappings\custom\keyboard.xml file, then manually change any mappings that you want, and make a backup (2) of that file again. Should you ever want to modify the mapping again using the setup program, replace the InputDeviceMappings\custom\keyboard.xml file with backup (1), make your changes, and re-apply all manual changes again. Kind regards, Ruud. [/QUOTE]