AFAIK it's not simple, due to the object selection (the conditions select objects that are affected by the actions) and the immediate conditions.It seems like a fairly simple thing to add into 2.5
AFAIK it's not simple, due to the object selection (the conditions select objects that are affected by the actions) and the immediate conditions.It seems like a fairly simple thing to add into 2.5
Awesome update guys! Can't wait to use it instead of extension! =D
But couldn't Fusion interpret the sub-event and break it down like it is separate? I can't imagine how that would effect things at all. Like just for the example provided:AFAIK it's not simple, due to the object selection (the conditions select objects that are affected by the actions) and the immediate conditions.
Fusion would see this internally as:
Climbing of "Active" = 0
Repeat while "D" is pressed
Climbing of "Active" = 0
Repeat while "A" is pressed
etc...
Instead of having to do anything special with it... Fusion would first select the active object being referenced, then it would look at the sub events and treat each one like a combine event with that object. Just running it from top to bottom like normal.
It's more or less just obfuscating that repetitive condition behavior so it stays behind the scenes and looks cleaner for the user. There's nothing really being changed in terms of object scope.
In your example it's simple. It becomes more complicated if you add conditions that also affect the selection of the objects selected by the parent condition, as the program has to remember and restore the objects selected by the parent condition before each sub-event.
But I'm saying don't have Fusion trying to read the weird sub-event structure... instead break it out into the normal structure it understands, and then read it that way. So there would technically be no programming changes needed to how the events are read and executed. You'd just need to program checks for sub-events and then have Fusion spit out events that it can handle easily.
The users sees:
Event 1
- Sub event 1
- Sub event 2
-- Sub-sub event 1
Fusion sees:
Event1
Event1
+Sub event 1
Event1
+Sub event 2
Event1
+Sub event 2
+Sub-sub event 1
Right? At what point would Fusion have to remember anything? What I'm getting at is that sub events aren't really actually doing anything other than being visually easier to read for the user. They aren't changing the scope of any objects.
Couldn't it just add the parent event(s) to all the child event(s) when "compiled" ?
So it'd be the same as manually adding those parent events to the children in the editor.
Edit: Yeah, like above. Sorry, seems that we posted at the same time :P
I see, yes it's certainly easier to do.
It will be awesome feature if at least instances of active objects will not be synchronized between them in editor.
Great update, thank you.
What do you mean?Originally Posted by LaurenceOliphant
Posting Permissions
Reply With Quote