setting up keyboard input with IR Suite 1.0.4.2 (1 Viewer)

charli181

Retired Team Member
  • Premium Supporter
  • August 3, 2007
    800
    111
    Sydney
    Home Country
    Australia Australia
    Hi all,

    I am trying to setup IR Suite to execute a macro when a key is pressed on the keyboard. (the letter "Z" for example). The keyboard I am using is integrated with the laptop. Will the new Keyboard Input support this and if so, how do I configure it.

    Note, when I click the detect button in the Input Service COnfiguration, the keyboard Input check box disappears. I am running Windows XP Pro, with last weeks SVN's. I do not have any IR devices as I control MP via the keyboard/mouse.

    Any help would be greatly appreciated as I been working on this all day and have got no where at all.
     

    and-81

    Retired Team Member
  • Premium Supporter
  • March 7, 2005
    2,257
    183
    Melbourne
    Home Country
    Australia Australia
    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,
     

    charli181

    Retired Team Member
  • Premium Supporter
  • August 3, 2007
    800
    111
    Sydney
    Home Country
    Australia Australia
    cheers Aaron, if you need any help in debugging this let me know.
     

    and-81

    Retired Team Member
  • Premium Supporter
  • March 7, 2005
    2,257
    183
    Melbourne
    Home Country
    Australia Australia
    hey,

    if you send me a private message with your email address I'll send you a test version.

    Thanks,
     

    Users who are viewing this thread

    Top Bottom