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
MediaPortal 1 Plugins
Generic Keyboard/Remote Input Plugin
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="rsenden" data-source="post: 328710" data-attributes="member: 24295"><p>Hi all,</p><p></p><p>Here are some answers and remarks for some of the previous posts:</p><ul> <li data-xf-list-type="ul">MediaPortal 'Key Pressed' action: By looking at the MediaPortal source, I think this doesn't actually generate a key press, but generates a MediaPortal 'key pressed' action event. If the specific MediaPortal feature actually listens for actual key presses instead of MediaPortal events, then the 'Key Pressed' action will not have any effect. By looking at the source, I think you can edit the Keyboard.xml file to use <action ... command="KEY" cmdProperty=" " ...> to actually send a space. See SendKeys method documentation (<a href="http://msdn.microsoft.com/en-us/library/8c6yea83(VS.85).aspx" target="_blank">SendKeys Method</a>) for valid cmdProperty values.<br /> </li> <li data-xf-list-type="ul">My test program seems to intercept key code 93 (context menu key) correctly, I will try to do some more testing with the actual plug-in in the near future.<br /> </li> <li data-xf-list-type="ul">The new keyboard handling mechanism uses a low-level keyboard hook. It is either this and being able to intercept as many keystrokes as possible, or using the original mechanism which intercepts only a limited set of keystrokes (no Win-keys and other special windows key combinations). The disadvantage of the new mechanism is that it may indeed influence other low-level keyboard utilities, has some issues with key pass-through, etc. I encountered a lot of problems with my own remote when using the new mechanism (for example keyup-events not fired), the current status is the best I've been able to get it so far. Of course, I will keep on tweaking the plug-in whenever I think I found an improvement (and as time permits). In a next version I will also add some more logging in order to help solving problems. Of course, any help with improving this plug-in is welcome.<br /> </li> <li data-xf-list-type="ul">I'm not sure whether this plug-in works with the latest SVN version; due to time constraints I only compile and test this plug-in against the latest released version (being 1.0 RC3).<br /> </li> <li data-xf-list-type="ul">Regarding any other questions, like learning additional keystrokes for a learning remote; I have no idea how to do this or whether it is at all possible.<br /> </li> </ul></blockquote><p></p>
[QUOTE="rsenden, post: 328710, member: 24295"] Hi all, Here are some answers and remarks for some of the previous posts: [LIST] [*]MediaPortal 'Key Pressed' action: By looking at the MediaPortal source, I think this doesn't actually generate a key press, but generates a MediaPortal 'key pressed' action event. If the specific MediaPortal feature actually listens for actual key presses instead of MediaPortal events, then the 'Key Pressed' action will not have any effect. By looking at the source, I think you can edit the Keyboard.xml file to use <action ... command="KEY" cmdProperty=" " ...> to actually send a space. See SendKeys method documentation ([url=http://msdn.microsoft.com/en-us/library/8c6yea83(VS.85).aspx]SendKeys Method[/url]) for valid cmdProperty values. [*]My test program seems to intercept key code 93 (context menu key) correctly, I will try to do some more testing with the actual plug-in in the near future. [*]The new keyboard handling mechanism uses a low-level keyboard hook. It is either this and being able to intercept as many keystrokes as possible, or using the original mechanism which intercepts only a limited set of keystrokes (no Win-keys and other special windows key combinations). The disadvantage of the new mechanism is that it may indeed influence other low-level keyboard utilities, has some issues with key pass-through, etc. I encountered a lot of problems with my own remote when using the new mechanism (for example keyup-events not fired), the current status is the best I've been able to get it so far. Of course, I will keep on tweaking the plug-in whenever I think I found an improvement (and as time permits). In a next version I will also add some more logging in order to help solving problems. Of course, any help with improving this plug-in is welcome. [*]I'm not sure whether this plug-in works with the latest SVN version; due to time constraints I only compile and test this plug-in against the latest released version (being 1.0 RC3). [*]Regarding any other questions, like learning additional keystrokes for a learning remote; I have no idea how to do this or whether it is at all possible. [/LIST] [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
Generic Keyboard/Remote Input Plugin
Contact us
RSS
Top
Bottom
