Normal
I've been using this a while now and am very pleased with it, thanks... However I've just recently upgrded to RC1 and have noticed that the following: When configuring this plugin the 'Add/Remove Buttons' section saves the Keyboard.xml config file to the old location for application data (C:\Program Files\Team MediaPortal\MediaPortal\InputDeviceMappings\custom). The Update Mapping' section however modifies the file in the new location (C:\Documents and Settings\All Users\Application Data\Team MediaPortal\MediaPortal\InputDeviceMappings). Hence to add new buttons and configure the mapping I have to first add the buttons, then copy the Keyboard.xml file from the old location to the new locations, and then update the mapping. I hope this helps anyone having similar trouble.
I've been using this a while now and am very pleased with it, thanks...
However I've just recently upgrded to RC1 and have noticed that the following:
When configuring this plugin the 'Add/Remove Buttons' section saves the Keyboard.xml config file to the old location for application data (C:\Program Files\Team MediaPortal\MediaPortal\InputDeviceMappings\custom). The Update Mapping' section however modifies the file in the new location (C:\Documents and Settings\All Users\Application Data\Team MediaPortal\MediaPortal\InputDeviceMappings). Hence to add new buttons and configure the mapping I have to first add the buttons, then copy the Keyboard.xml file from the old location to the new locations, and then update the mapping.
I hope this helps anyone having similar trouble.