States = Visited but not working
Aug 21, 2021
Hi All,
I am creating a storyline that has 5 different modules (scenes) within it. There is a 'contents page' slide that has the 5 modules listed and I have created a trigger for each module text box that jumps to the start of that corresponding scene when clicked. I have set these text boxes so that the state of them changes to 'visited' when 'Topic01Complete = True' and so on. I've then added a trigger at the end of each slide in each scene that changes 'Topic01Compelte = True' when they get to that slide. However, for some reason when i click on each text box the state is immediately changing to 'visited' as opposed to waiting until I actually get to the slide which the condition set. Does anyone know why this would be?
1 Reply
All the built-in states (including Visited) have hard-wired superpowers to allow them to perform their functions, without bothering you to create triggers for them.
Visited's superpower is to change any object with a Visited state to Visited when it is clicked. Not only is it unnecessary to create a trigger to change an object to Visited, It is dangerous. Your trigger may conflict with the built-in one, and cause unwanted consequences.
To do what you are describing, create a custom state, and set your text boxes to change to your custom state, instead of Visited.
For a sample, check the Restricted or Mixed Navigation in the sample at this post:
https://community.articulate.com/discussions/articulate-storyline/free-sample-restricted-and-free-random-navigation-using-variables-and-triggers
It has four buttons that take the learner to different slides (the way you want to go to different scenes), and when they are all visited, a button appears that can have any trigger on it you want. In the restricted navigation, the four buttons appear in order, only after the previous one is visited, while in Mixed, they can be visited in any order.