Reply to thread

Message

<blockquote data-quote="rsenden" data-source="post: 811816" data-attributes="member: 24295">Regarding the weird results on your main MP installation, do you have a log file for that? On the computer that fails only 1 of 30, did you try both the regular version of the plug-in and the DLL attached in my previous post? Does the test-DLL give the same weird results on that PC, or does it work the same or maybe even better than the regular version?I will do some more testing myself, unfortunately I can only test on my development laptop with a regular keyboard (even though that shouldn't make a big difference, it isn't really production-like). My HTPC is still running WinXP so the problem doesn't occur there. If it were running Win7, this plug-in would probably be useless as my HTPC is low-end (Celeron 2.66, 512MB memory) <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" />.If other people are willing to test (or help look into this problem), that would be appreciated.Edit:I now also encountered the weird behavior. Attached to this post is a zipped DLL that seems to work better. Again, in order to use this DLL, make a backup copy of the original KeyboardInputPlugin.dll in \Program Files\Team MediaPortal\MediaPortal\plugins\process (make sure to give it a non-DLL extension and/or move the backup copy to another directory) and then replace it with the attached DLL. Can you please try it and let me know the result?\Edit: Removed DLL; a new version of the plug-in has been released which incorporates these and other changes.</blockquote>

[QUOTE="rsenden, post: 811816, member: 24295"] Regarding the weird results on your main MP installation, do you have a log file for that? On the computer that fails only 1 of 30, did you try both the regular version of the plug-in and the DLL attached in my previous post? Does the test-DLL give the same weird results on that PC, or does it work the same or maybe even better than the regular version? I will do some more testing myself, unfortunately I can only test on my development laptop with a regular keyboard (even though that shouldn't make a big difference, it isn't really production-like). My HTPC is still running WinXP so the problem doesn't occur there. If it were running Win7, this plug-in would probably be useless as my HTPC is low-end (Celeron 2.66, 512MB memory) :D. If other people are willing to test (or help look into this problem), that would be appreciated. Edit: I now also encountered the weird behavior. Attached to this post is a zipped DLL that seems to work better. Again, in order to use this DLL, make a backup copy of the original KeyboardInputPlugin.dll in \Program Files\Team MediaPortal\MediaPortal\plugins\process (make sure to give it a non-DLL extension and/or move the backup copy to another directory) and then replace it with the attached DLL. Can you please try it and let me know the result? \Edit: Removed DLL; a new version of the plug-in has been released which incorporates these and other changes. [/QUOTE]

Verification