> Basically, it sends one keystroke when the button goes down, then another when the
> button goes back up-- state changes, in other words, instead of continuously sending
> the button when held. Same goes for the joystick directions, with on and off
> keystrokes for each.
That's odd. My understanding was the keyboards always have worked that way. MAME wants to see key-down and then no key-up until you've actually let go, and that's precisely the interface both DirectInput and the traditional Windows message API present. Games (and MAME) disable key auto-repeat, because the keyboard implements that by sending key-down (wait) key-up/key-down (wait) key-up/key-down (repeat) and that would of course be harmful to games.
I guess I'll read the Ars article in case you aren't quoting it properly 
|
Index 
Flat 
Re: Not terribly likely as it stands-- read within.
Reply
