Reply to thread

Message

<blockquote data-quote="and-81" data-source="post: 240552" data-attributes="member: 11844">hey there,The Keyboard Input plugin deliberately does not activate when you click Detect.&nbsp; This was a decision I made, though I may change it in the future. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Basically, if you just put a check in the box next to it in the Input Service Configuration and then test it by opening up Debug Client and click Connect on it.Then start pressing buttons on your keyboard and you should see a code a unique to each keypress pop up in the list.&nbsp; This will prove it's working.The all you need to do is create new button mappings in either Translator or MP Control Plugin for the button you want to use.Of course, everything I just said is what you should do when I post the next test version...&nbsp; Because while I've been typing this up I've been testing the procedure and found a bug in the Keyboard Input plugin ...I'm sorry to waste your time mate, I really am.&nbsp; I tested the keyboard input plugin before I added it to the installer, but I never tested it with the production environment ...I'll fix it now and post an update as soon as I can.EDIT: Additional info...The problem turns out to be that you can't trap keyboard input in a windows service.&nbsp; Windows Services start before the user is logged in, so if I could intercept keyboard input I could intercept the login process.To debug the plugins I use an Application version of the Input Service for almost all my testing.&nbsp; This is the first difference between the two that I've found.But the solution is going to suck...&nbsp; Either switch back to an application and not a service, or make a small application to do the&nbsp; keyboard hook.I'll start by making a small app to do the keyboard hook and see how that goes...Cheers,</blockquote>

[QUOTE="and-81, post: 240552, member: 11844"] hey there, The Keyboard Input plugin deliberately does not activate when you click Detect. This was a decision I made, though I may change it in the future. :) Basically, if you just put a check in the box next to it in the Input Service Configuration and then test it by opening up Debug Client and click Connect on it. Then start pressing buttons on your keyboard and you should see a code a unique to each keypress pop up in the list. This will prove it's working. The all you need to do is create new button mappings in either Translator or MP Control Plugin for the button you want to use. Of course, everything I just said is what you should do when I post the next test version... Because while I've been typing this up I've been testing the procedure and found a bug in the Keyboard Input plugin ... I'm sorry to waste your time mate, I really am. I tested the keyboard input plugin before I added it to the installer, but I never tested it with the production environment ... I'll fix it now and post an update as soon as I can. EDIT: Additional info... The problem turns out to be that you can't trap keyboard input in a windows service. Windows Services start before the user is logged in, so if I could intercept keyboard input I could intercept the login process. To debug the plugins I use an Application version of the Input Service for almost all my testing. This is the first difference between the two that I've found. But the solution is going to suck... Either switch back to an application and not a service, or make a small application to do the keyboard hook. I'll start by making a small app to do the keyboard hook and see how that goes... Cheers, [/QUOTE]

Verification