[betaalanine]

So the client has built-in functionality that only allows modifier and action keys to remain pressed, which is good for the inexperienced user. It, however, means things such as enchanting bolts and cooking karambwans can't be done because those keys cannot be held and only typed.

While the scope of it is small, it is a limitation that should be addressed I feel.

 

[savior]

The keys do remain pressed if the release method isnt called, however holding down a key on your actual keyboard makes your operating system type the key over and over again, including releasing it. So the runescape client ends up getting many key presses and that's what allows you to go through a dialog for example with holding down the space bar.

 

[betaalanine]

The keys do remain pressed if the release method isnt called, however holding down a key on your actual keyboard makes your operating system type the key over and over again, including releasing it. So the runescape client ends up getting many key presses and that's what allows you to go through a dialog for example with holding down the space bar.

So your example of it being sent over and over again is not exactly right. It does get sent again and again for the keyPressed event, but until it's released it will never send the keyTyped or keyReleased event.

However, what I'm talking about isn't that. You can try it for yourself with the shift key vs the 2 key. The shift key will remain pressed until the released method is called, whereas 2 will only get pressed once. The reason for that is in the actual press method. If you view the code for it you can see it only allows certain keys to remain pressed and will automatically "type" out a key if it's not one of those that are allowed.