Have I found a bug or made an oversight in my slide design? Can I get someone to verify this?
My trigger says "Change state of the next button to Disabled when Timeline starts".
To enable, "Change the state of next button to Normal when the user clicks Hotspot1"
I have set the slide properties to "Resume saved state".
But when I Prev back to this slide, even after having completed the hotspot click, the Next button disables anyways.
To enable it, I must click the hotspot (top of the slide, right of the Clean zone text)
My conclusion is that either 1) Storyline 360 does not observe it's own "Resume saved state" since the trigger to disable the Next button is fired when I revisit the slide anyways.
2) I made an oversight in the way I designed this function, so how can I make work as intended? Once users have completed the task, I do not want to disable the Next button any more.
Ok, I get around this WAE-issue by tying the trigger to a condition that checks the the state of something. Now the Next button is not disabled when you flip back to here here.
Another way to get around this issue is to not use the trigger to set the next button to disabled when the timeline begins. If you have something on the slide that changes states when the user clicks on it, you can tie that visited state to the use of the next button. I don’t think hotspots have states. You can instead add a shape over the area on the screen the user needs to click on and give that shape an additional state called visited. Make the shape have no outline and make the fill color 100% transparent. Then set a trigger for the next button that says jump to next slide when user clicks the next button and condition of shape state is not equal to normal.
5 Replies
Even when a slide resumes a saved state it will still fire the timeline start triggers, this is expected behaviour.
To get round this you will need to set a condition to the trigger that sets the button to disabled either based on a variable or a state
Quick answer, thanks.
What does "Saved state" scope to if it doesn't mean the saved state? Saved state EXCEPT the following n conditions?
1) On timeline start triggers still trigger?
Anything else that Saved state scope doesn't include that I should be aware of?
It is resuming to saved state but the triggers also fire every time you resume the slide so the Next button gets disabled again.
Timeline start triggers always fire irrespective of the slide state, I don't think there is anything else.
Ok, I get around this WAE-issue by tying the trigger to a condition that checks the the state of something. Now the Next button is not disabled when you flip back to here here.
Another way to get around this issue is to not use the trigger to set the next button to disabled when the timeline begins. If you have something on the slide that changes states when the user clicks on it, you can tie that visited state to the use of the next button. I don’t think hotspots have states. You can instead add a shape over the area on the screen the user needs to click on and give that shape an additional state called visited. Make the shape have no outline and make the fill color 100% transparent. Then set a trigger for the next button that says jump to next slide when user clicks the next button and condition of shape state is not equal to normal.
This discussion is closed. You can start a new discussion or contact Articulate Support.