Event Arguments do not behave as expected
Posted: 09 Sep 2013, 16:15
Here's something that I can't figure out:according to the manual I can use Event-Arguments to discern different events.... very handy to e.g. see which button was pressed: you assign an Argument to each of the Button-Pressed-Events, collect all the Events at one central Event (i.e.: the event can be triggered by many others) and read out the Argument received. So far so good.
But...
This method becomes completely unpredictable when using more than one Event--Event connection, or when you want to make a "jump" out of a Container (exposed Events) even when you manually "carry" the Event Argument.
It's not easy to explain... I've built a small example (Ventuz 3 Pro) so you can see what I mean. Note that the Event Argument sometimes is carried immediately (but only to some nodes, even though they're daisy-chained) or is carried to all synchronously -- but buffered until the next Event is invoked.
Is this behaviour actually intended?
sq.
But...
This method becomes completely unpredictable when using more than one Event--Event connection, or when you want to make a "jump" out of a Container (exposed Events) even when you manually "carry" the Event Argument.
It's not easy to explain... I've built a small example (Ventuz 3 Pro) so you can see what I mean. Note that the Event Argument sometimes is carried immediately (but only to some nodes, even though they're daisy-chained) or is carried to all synchronously -- but buffered until the next Event is invoked.
Is this behaviour actually intended?
sq.