Thanks for 2.5+ guys, it's great, the perfomance boost is huge in my case and child events are gold!
Now that we can use behaviors with no constraints, i'm trying to figure out the benefits in terms of speed.
Can someone at Clickteam tell us how the behaviors works inside the runtime and if there is a difference of performances?
There is no difference between behaviors and frame events. Behavior events are simply pasted at the end of the frame events (after global events) when you run or build the application.
A couple of mistakes in your benchmark app:
1. You do a On loop "normal" instead of "behav" in the behavior
2. You do not need to multiply the behavior time by the number of objects, the behavior is not executed for each object, it's executed like frame events.
Yes I just saw the error, thanks for the quick answer! So there is no difference for object scoping either I imagine?
Correct, there is no difference.
One thing that I would love is to be able to send objects in the event editor to the left. When I have a big project I can have hundreds of objects so I have to scroll a looong way to find the object I want to work on. If I could just find it, right click on it and select something like "send to left" and it would appear all the way to the left in the order on the event editor it would make things much easier! (Even better if it also would be sorted first when finding objects when refering to objects where you have to find it among all the objects)
Hey Clickteam, congratulations for the release of 2.5+, these are much-asked-for improvements that users have been waiting for years literally. Can't wait to play with them.
Also big thanks to the team for sorting out my Key Conversion request very swiftly this time around. To those who might see this post from a keyword search - yes, at the the time of this writing, the Key Conversion service can be used and it's how I converted my Steam copy of 2.5+ to standalone 2.5+.