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="Markos" data-source="post: 811605" data-attributes="member: 82319"><p>The real issue is not that the plugin is slow. The keyboard hook timeout is long enough to process the lookup, this has been discussed many times.</p><p></p><p>What actually happens is that when Windows is low on resources, it starts to page data, which occurs in thrashing. Even if the plugin processes each message in few milliseconds, the thrashing can cause mediaportal to stop responding for few seconds. If that happens, windows decides to stop posting messages (without even knowing that windows' paging mechanism itself caused the slow response).</p><p></p><p>If you want to read little bit more about this, check <a href="http://stackoverflow.com/questions/3891750/did-ms-change-something-about-keyboard-hooks-in-windows-vista-or-7" target="_blank">winapi - Did MS change something about keyboard hooks in Windows Vista or 7? - Stack Overflow</a> and the top answer.</p></blockquote><p></p>
[QUOTE="Markos, post: 811605, member: 82319"] The real issue is not that the plugin is slow. The keyboard hook timeout is long enough to process the lookup, this has been discussed many times. What actually happens is that when Windows is low on resources, it starts to page data, which occurs in thrashing. Even if the plugin processes each message in few milliseconds, the thrashing can cause mediaportal to stop responding for few seconds. If that happens, windows decides to stop posting messages (without even knowing that windows' paging mechanism itself caused the slow response). If you want to read little bit more about this, check [url=http://stackoverflow.com/questions/3891750/did-ms-change-something-about-keyboard-hooks-in-windows-vista-or-7]winapi - Did MS change something about keyboard hooks in Windows Vista or 7? - Stack Overflow[/url] and the top answer. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
Generic Keyboard/Remote Input Plugin
Contact us
RSS
Top
Bottom