Forum Discussion
Storyline 360 - Visited states seem a bit buggy
PROBLEM: It would appear that the 'visited' state is not as consistent in SL360 compared to SL2. I want to know whether this is just my experience (i.e. my files), or whether other people are experiencing it (a bug).
(simplified) USE CASE: As a user, I arrive on a page that has 3 buttons that link out to other slides. The trigger disables the 'Next' button when the timeline starts. When I click each button, it goes to a 'visited' state. When all 3 buttons are visited, the Next button becomes 'Normal'.
MY NOTES: I use this technique (Visited State) because variables are 'one-layer-down' on the GUI, and therefore are not as efficient to manage for maintenance and changes. They also require higher level technical skills (cost/time).
Long-story-short is, I'm being forced to use the more inefficient method of variables because the States trigger is haphazard and doesn't work 'first-time-every-time' (even though I template the slides to use the same setup every time).
21 Replies
Nicely written up Tim - thanks for sharing here.
Yes, thank you!
Hello Jamie - It looks like based on Tim's case, we have shared this issue internally for further review. We are working to prioritize issues based on user impact and based on this thread and a few support cases, I have upped the priority of this issue, but I do not have an update at this time.
I've also attached this thread so that we can share an update here when available.
Hi all!
We released another update for Storyline 360 (Build 3.52.25156.0) today, which included a fix for the bug where a trigger that changed the state of an object after visiting other objects didn't work when the trigger was on a layer.
Update Storyline 360 in your Articulate 360 desktop app to take advantage of the newest fixes and features.
If you have any questions, you can reach our team in this discussion or in a support case.
