I've had this problem forever with Delphi,
but not until recently tried to fix it.
If the player hits five or six keys at the same time, the app pauses.
Any way around this?
I've had this problem forever with Delphi,
but not until recently tried to fix it.
If the player hits five or six keys at the same time, the app pauses.
Any way around this?
Hard to say other than this is a physical design flaw of keyboards. Depending on what paths the key's take they can "meld" or merge signals when too many are pressed, usually above 3 keys for current models and about 5 for high quality, older models.
Yes, tell the player not to do thatOriginally Posted by aidave
.
<br /><br />There are a lot of people who are dead while they are still alive. I want to be alive until the day I die.<br />-= Paulo Coelho =-
hmm
1 - Move Forward
2 - Strafe
3 - Jump
4 - Walk (shift)
5 - Fire weapon 1
6 - Fire weapon 2
in the heat of battle all these keys are often pressed at the same time
What does your process code look like? This can make all of the difference in the world. Also what are you using to process keyboard commands?
- Jeremy
http://www.eonclash.com/
It's sure not the "acessibility" option of WinXP kicks in?.. It could've thought your player had a finger disability and helpfully tried to "aid" him. :evil:
This is often deactivated. It's the hardware design of the Keyboard preventing additional signals along the wires inside to prevent loss of a certain signal.
But why then when I tried to press a dozen keys testing my app it didn't pause anything, just omitted the extra key press messages?
Maybe this is the reason: when keyboard is "overloads", the number of press/release messages sometimes doen't match each other.
No. There are certain keys on the same wire pair, and the keycodes get scrambled if you press too many. Try pressing keys in the same 'column' such as '2WSX'. To prevent the overcrowding of signals, the keyboard limits them to roughly 3 per wiring set. Thus the omission.
Posting Permissions
Reply With Quote
Bookmarks