[1.46] more/better events

my suggestion:

more/better events for keys, like that:
key_pressed
key_released

this would allow for key combinations. i dont think thats possible in an easy way

or something like: keys.isBeingPressedNow( keys.crtl and keys.f )



please leave a reply with what you think

keys_beingpressednow doesn't sound so much like an event. The problem is that an event has to be an event.

Key release events have been discussed repeatedly, and the difficulties with them discussed. I personally fail to even see the point in the first place. You can make a perfectly reasonable key combo by having a key set up the next key event to be a second key, and a third after that, for as long as you want. It seems to me that the only point of wanting a key combo based on key release is to make sure that people have to hold down both keys at the same time, so it is just a little harder to press the key combo you define. What exactly is the point of that? Why shouldn't Ctrl+v or whatever give you a break on pushing down the control key? Just to ensure maximum risk of carpel tunnel damage, or is there some actual benefit?

it would be great for games. that way as long as you hold down 'w' (or whatever the forward key would be) you move forwards etc, you can have popup menus that only show as long as you hold down ctrl etc. it would be quite useful in my opinion but you are right:

ChunLing, on 24 October 2012 - 11:02 AM said:

Key release events have been discussed repeatedly, and the difficulties with them discussed.

I think it would be okay for games. But you already get multiple key/char events by holding the key down.

Also, if any of you are really wanting to damage my wrists that badly, you can tell if a key is being held down in combination with any of the character keys (letters and stuff) because it prevents the "char" event from following the key event.

the multiple events have a significant delay after initial key press. it is a serious issue in fast paced games.

I didn't know the char event did not follow if the key is still held in…

Neither did I. I don't know if it only works for command keys or if it works for other keys as well, something to check.

If the char event did not follow, then when you held down a key in the terminal it wouldn't repeat.

So if you get a command key, then you can set a timer event, and if you then get the second key in the combo, but not a "char" event before the timer event fires, you have a combo. I can't believe myself, I'm telling people how to do this.

I'm also saying NOT to do it, it's annoying. If you have a super command that exits the program (there already is one) or reboots the computer (there's on of those too) or sets off a nuke in your base (and thank Cloudy there isn't one of those, unless you add it) which you don't want pressed by accident, then fine. But normally, key combos are just annoying.