Reply to thread

Message

Hello, i made some analysis with process monitor. That's all i can do for now.
The plugin does indeed write the config file in the right place with user management active. It does search the file in the right profile folder and it does save the configuration.

When the program loads, it search the config file first on
C:\ProgramData\Team MediaPortal\MP2-Client\Config\MediaPortal.Plugins.InputdeviceManager.InputmanagerSettings.xml
and when you log in it does open the file in
C:\ProgramData\Team MediaPortal\MP2-Client\Config\b9bccb93-008f-4a5b-a85d-f86245cd0137\MediaPortal.Plugins.InputdeviceManager.InputmanagerSettings.xml.

[ATTACH=full]197218[/ATTACH]

The only problem is that it seems somehow not to register the keybindings on subsequent reboots until you first map a new key.
Is it possible to enable further debugging during the plugin key binding at startup? Or when it's listening and find a new input?

EDIT: I tried to copy the same InputManagerSettings.xml with the right keybindings in all the directories where it looks for it but still no luck.

<blockquote data-quote="Alberto83" data-source="post: 1242996" data-attributes="member: 128278">Hello, i made some analysis with process monitor. That's all i can do for now.The plugin does indeed write the config file in the right place with user management active. It does search the file in the right profile folder and it does save the configuration.When the program loads, it search the config file first onC:\ProgramData\Team MediaPortal\MP2-Client\Config\MediaPortal.Plugins.InputdeviceManager.InputmanagerSettings.xmland when you log in it does open the file inC:\ProgramData\Team MediaPortal\MP2-Client\Config\b9bccb93-008f-4a5b-a85d-f86245cd0137\MediaPortal.Plugins.InputdeviceManager.InputmanagerSettings.xml.[ATTACH=full]197218[/ATTACH]The only problem is that it seems somehow not to register the keybindings on subsequent reboots until you first map a new key.Is it possible to enable further debugging during the plugin key binding at startup? Or when it's listening and find a new input?EDIT: I tried to copy the same InputManagerSettings.xml with the right keybindings in all the directories where it looks for it but still no luck.</blockquote>

[QUOTE="Alberto83, post: 1242996, member: 128278"] Hello, i made some analysis with process monitor. That's all i can do for now. The plugin does indeed write the config file in the right place with user management active. It does search the file in the right profile folder and it does save the configuration. When the program loads, it search the config file first on C:\ProgramData\Team MediaPortal\MP2-Client\Config\MediaPortal.Plugins.InputdeviceManager.InputmanagerSettings.xml and when you log in it does open the file in C:\ProgramData\Team MediaPortal\MP2-Client\Config\b9bccb93-008f-4a5b-a85d-f86245cd0137\MediaPortal.Plugins.InputdeviceManager.InputmanagerSettings.xml. [ATTACH=full]197218[/ATTACH] The only problem is that it seems somehow not to register the keybindings on subsequent reboots until you first map a new key. Is it possible to enable further debugging during the plugin key binding at startup? Or when it's listening and find a new input? EDIT: I tried to copy the same InputManagerSettings.xml with the right keybindings in all the directories where it looks for it but still no luck. [/QUOTE]