New event conditions - just a single button press

GDevelop general Feature requests
#1

Hey there.

Thanks for the hard work with the software, I find it very useful.

There is still one major flaw with the event functions, which is the incapability to just press once keyboard/joystick/mouse buttons instead of holding them down. There should be different events for holding the key down and for single presses.

Now I know this can be done with variables, but the thing is, it’s not accurate and it doesn’t register the value changes fast enough. For example in a platforming game, the player presses “jump” button and changes the value “jump button down” to 1. When the “jump button down” is 1, the character will not jump during this. Then the player releases the “jump” button, the value goes to 0 and now the character can jump again. The Problem is that the value does not change fast enough and this causes inaccuracy and usually the game fails to register rapid “jump” button presses.

This issue was already discussed here to some extent:
http://translate.googleusercontent.com/translate_c?act=url&depth=1&hl=en&ie=UTF8&prev=_t&rurl=translate.google.com&sl=fr&tl=en&u=http://www.forum.compilgames.net/viewtopic.php%3Ff%3D16%26t%3D2557%26sid%3Dff0c403e028b270a10079c385bca80fe&usg=ALkJrhgb7yPL89Kq-NnLX8rX0hOFbujnVA

I think this would be an useful addition and I’m sure there’s plenty of people who agree with me. I know that scirra construct already has these features and they work really well.

Thank you for taking the time to read this, I really do hope I made some sense.

#2

I must admit that such conditions will be useful indeed.
But please note that there is no difference between using a variable to do this on your side or using function integrated into Game Develop ( that’s why there is, for now, no such conditions : Events can perfectly be doing a such job ).
I mean that, when you say that “The Problem is that the value does not change fast enough and this causes inaccuracy and usually the game fails to register rapid “jump” button presses.”, maybe there is a glitch somewhere, but it is not related to using variables to ensure that a key has just been pressed. Really, when you add an action to modify a variable, it is really modified as soon as the action is executed, and the other events are not executed as long as the variable is not internally modified, so it is impossible to have accuracy problem in this context.

But well, I’ll try to add prebuilt conditions to the next version. :slight_smile: