The eventsheet is read every frame (60 times per seconds), from top to bottom.
An event (a line) is made of 2 parts :
the left part, the condition(s),
and the right part, the action.
If the condition(s) is true, then the action is executed.
But the condition does something else very important, which is Object picking ! Consider it like a filter : only the objects which have been picked (for which the condition is true) are available to the actions on the right side.
For exemple, if you check the collision between the PurpleCoin and the GreenCoin, on the right side, the actions will be applied to the Purple et Green coins which collide.
Now come the subevents :
A subevent is only tested if the condition of the event it is attached to is true. AND it is only applied to the objects which have been picked in the event it is attached to.
For exemple : a subevent attached to the one described previously, will only perform the condition on the Purple and Green coins which collide (which had been picked in the previous event).
And this is a huge difference with an new event, created below another but which is not a subevent ! Contrary to a subevent, this new event would be tested independently of the previous one (whether the conditions of the previous one are meet or not), and it will take into account every objects (the object picking from previous event is reset).
Said differently : a condition also filters the objects available for the actions. A subevent adds a new filter to the previous one, while a new event (which is not a subevent) resets the filter.
I hope that it makes sense It is a key concept in Gdevelop, which is easy to miss when starting. And which very different from most other programming tools.
I thought the first global variable EndX and EndY would record the first position of purplecandy, but it follows purplecandy and returns the position of where purplecandy ends up. The the second global variable StartX and StartY records the first position of purplecandy???
Generally, the drop event is used to figure out the target position, then a tween is used to move to the target position (or back to the original position if determined by the game rules).
Note that in this case the tween is just a nice way to animate the object movement. I didn’t include it in my example because that wasn’t the focus of the example.
You mean released on the gdevelop gaming site? Because I just starting learning a couple of months ago, the gdevelop site is the only place that I am serving all my games to.
I meant, that if your ipad says “in full screen swipe down to exit”, it will be a problem, not only for you but to anyone who uses ipad and tries to play the game in fullscreen.
It is a key concept in Gdevelop, which is easy to miss when starting. And which very different from most other programming tools.
