Re: A DirectInput problem

> I'd say you should try with a
> different keyboard, perhaps you have a ghosting problem in the
> hardware.

Same problem with different keyboards in the office and at home. Hmm. Will 
try with other ones if I can.

> On another note, I've never used DirectInput for keyboard or
> mouse. IME, I've had more robust results and a simpler solution by
> intercepting the keyboard/mouse events (WH_GETMESSAGE, WH_CALLWNDPROC
> - both need to be checked at the same time) directly for keypresses
> and GetCursorPos() for mouse position.

Hmmm, why not WH_KEYBOARD or WH_KEYBOARD_LL ?

I tried WH_KEYBOARD but it has the same problem as DI anyway. Sigh.

- Pierre 


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Gamedevlists-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gamedevlists-general
Archives:
http://sourceforge.net/mailarchive/forum.php?forum_id=557