Forms.Keys vs DirectInput

I know its probably just me, but is there any reason that OnKeyDown can only process one key down at a time

I should add that I am used to using DirectInput for this kind of thing, but I see that it's being recommended not to use it any more, so I tried using OnKeyDown, but when I hold down 2 keys at once, only one gets processed even though my code looks like:

if (e.KeyCode = Keys.W) moveforward();

if (e.KeyCode = Keys.A) moveleft();



Answer this question

Forms.Keys vs DirectInput

  • JustinRC

    Nightmare_BE wrote:
    BLiTZWiNG wrote:

    This leaves me wondering how to handle joystick and other device input if DirectInput is being phased out

    Don't think DirectInput is phased out ... i still use it. If they phase it out older games using directinput would not work anymore.

    This may be true, and I guess I should stop fussing over trying to do it "properly" and go back to using DInput, but I'd certainly like David Weller to expand upon his comments in this thread..

    http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=278599&SiteID=1


  • Arup

    Ok I see the solution is probably to use GetAsyncKeyState (the method I used to use back in the days of DirectX 2..)

    This leaves me wondering how to handle joystick and other device input if DirectInput is being phased out


  • suryavbnet2005

    BLiTZWiNG wrote:

    This leaves me wondering how to handle joystick and other device input if DirectInput is being phased out

    Don't think DirectInput is phased out ... i still use it. If they phase it out older games using directinput would not work anymore.


  • Forms.Keys vs DirectInput