F3der1co

suggestion:  change the data dropdown to checkboxes like the add child action: x y angle

I just had broken collision with jump through platforms and just remembered reading about this here! I would have not figured this out without hours/days of search if it wasn't...

just realized that maybe it is also relevant how to create the two red elses, as I guess the top else shouldn't have been red to begin with, one way...

imho filtering the list depending on what is typed would be a decent solution. I think in a more realistic project it is a lot less likely to have that...

probably not feasible depending how the browser does the layouting. But doing it asynchonously would be cool. So the user can keep typing while the autocomplete is loading.

 This is a severe bug imo, this can lead to nearly impossible to track down issues, as shown in this example. This can lead to stuff being awaited from...

My take is that even in the first example you gave it should not wait for the timeline. Sub-events should not suddenly break their scope like that and this design...

I mean construct does follow this strict scoping, i.e. with picking or local variables etc. This tween/timeline case is an outlier that breaks this rule in a counter intuitive way....

There is no hierarchy in this repro. here you can visually see the slowdown (its smooth in all direction except down), it also shows up in the chrome performance profiler....

It seems to only reproduce for me in chrom (I'm on 127.0.6533.120). Edge works fine. I tried resetting chrome but it didn't fix it. I'll investigate further