Reply to thread

Message

Hi Enchant

I have this plugin running successfully, mostly because I was never able to get the Shortcuter plugin to work for me. In your case the main problem seems to be finding out where MP is trying to read the "keyboard.xml" file from. The trick that I have used many times in trying to find out what MP was doing is to use Process Monitor. It's a free tool that you can easily find with Google. Just set it to filter out all events so that it only shows you events on the parameter "path", containing "keyboard.xml", then start MP with Process Monitor in the background and the plugin enabled. If you then exit MP again, you should have an entry in Process Monitor telling where MP was trying trying to read the file from.

Regarding the layers and conditions, I never figured out how that works, but I use this plugin to map shortcuts to things like TV series, recorded TV etc. to "CTRL-ALT + any letter" keyboard shortcuts, and those shortcuts are produced by my iMon remote driver.

As far as setting things up I never used the config tool for the plugin in the normal way because it kept crashing on me. I only used it to figure out which numeric code had to go in the XML file for any given key-combo. It shows that live somewhere in the tool whenever you press a key. Then I just edited the XML file in notepad.

If you need any more info, just let me know.

<blockquote data-quote="Mercbac" data-source="post: 277665" data-attributes="member: 48233">Hi EnchantI have this plugin running successfully, mostly because I was never able to get the Shortcuter plugin to work for me. In your case the main problem seems to be finding out where MP is trying to read the &quot;keyboard.xml&quot; file from. The trick that I have used many times in trying to find out what MP was doing is to use Process Monitor. It's a free tool that you can easily find with Google. Just set it to filter out all events so that it only shows you events on the parameter &quot;path&quot;, containing &quot;keyboard.xml&quot;, then start MP with Process Monitor in the background and the plugin enabled. If you then exit MP again, you should have an entry in Process Monitor telling where MP was trying trying to read the file from.Regarding the layers and conditions, I never figured out how that works, but I use this plugin to map shortcuts to things like TV series, recorded TV etc. to &quot;CTRL-ALT + any letter&quot; keyboard shortcuts, and those shortcuts are produced by my iMon remote driver.As far as setting things up I never used the config tool for the plugin in the normal way because it kept crashing on me. I only used it to figure out which numeric code had to go in the XML file for any given key-combo. It shows that live somewhere in the tool whenever you press a key. Then I just edited the XML file in notepad.If you need any more info, just let me know.</blockquote>

[QUOTE="Mercbac, post: 277665, member: 48233"] Hi Enchant I have this plugin running successfully, mostly because I was never able to get the Shortcuter plugin to work for me. In your case the main problem seems to be finding out where MP is trying to read the "keyboard.xml" file from. The trick that I have used many times in trying to find out what MP was doing is to use Process Monitor. It's a free tool that you can easily find with Google. Just set it to filter out all events so that it only shows you events on the parameter "path", containing "keyboard.xml", then start MP with Process Monitor in the background and the plugin enabled. If you then exit MP again, you should have an entry in Process Monitor telling where MP was trying trying to read the file from. Regarding the layers and conditions, I never figured out how that works, but I use this plugin to map shortcuts to things like TV series, recorded TV etc. to "CTRL-ALT + any letter" keyboard shortcuts, and those shortcuts are produced by my iMon remote driver. As far as setting things up I never used the config tool for the plugin in the normal way because it kept crashing on me. I only used it to figure out which numeric code had to go in the XML file for any given key-combo. It shows that live somewhere in the tool whenever you press a key. Then I just edited the XML file in notepad. If you need any more info, just let me know. [/QUOTE]