Forum Discussion
Storyline 360 - Visited states seem a bit buggy
Tim,
I've been saying since SL2 was new that "State of ... is ..." is not an action, therefore it does NOT belong in the "When" part of a trigger. There is literally nothing for the trigger to monitor that will initiate its action. Most of us read it as State BECOMES, which is an action. It would be great if the programmers would make it a true ""State of ... BECOMES...", because then the trigger would have some action to initiate it, and we could use it.
I suspect that when an action occurs (like a click) the slide runs through the list of triggers, checking the list of actions to monitor. If it is reading that exact trigger and the states are all true at that exact instant, it fires, because sometimes the "State of ... is ..." actually functions correctly. If the state hasn't changed yet when it gets to that trigger, it fails, as your project proves. It doesn't come back to the list, because the change of state itself apparently doesn't raise an action.
If the timing isn't exactly perfect (the user is lucky), it doesn't work. Your sample is the best evidence I have to support that theory. Thank you for isolating this problem. I will be starting a support case.
As to the exact reason why this doesn't work, it is the other triggers. By the time an object runs through those other triggers, and reports that its state has changed, the slide has run through it list of triggers, checked the "State ... of ... is", found it not true, and ignored it. Until the programmers make a change of state raise an event, it is not a reliable action for the When portion of a trigger.
BTW, it works great in conditions, where it belongs.
Hi Walt,
Thanks, and I would tend to agree, except that just moving the objects onto the Base instead of a layer, will also remove the issue, so therefore it's not the triggers, or the order of the triggers that is creating the problem.
And, if I build it from scratch, it works fine. This is definitely a bug. A corruption is occurring somewhere in the pipeline that stops it from working as expected.
I have submitted a case, because for me, I need to know the origins of the bug. It's costing me a lot of time and effort.
And for me, building products is all about efficiency. In order of time/effort to create and maintain, my order of preference for this type of functionality is:
1. Build it as a State Trigger event
2. Build it as a condition within a Trigger event
3. Build it as a Trigger event based on a variable
Cheers.