I have a project which has 10 layers (including base). I have created a seamless interaction where the learner clicks each tab and transitions to each layer for information. Since there are multiple tabs tabs to visit I want them to be able to see which ones they have clicked on previously without returning to the base layer. How can I carry the visited state of a button from one layer to the next? Attached is the slide to which I am referring.
It can be relatively simple. First, the built-in states, like Visited, have their triggers built-in, so if you create one of them, it functions without the need of any further action from you. In fact, if you write a trigger to perform that function (like "Set state to visited when clicked"), it will most likely conflict with the built-in trigger, producing strange, but seldom wonderful results.
The simplest way to show which layers are visited is to use the visited state of the buttons on the base layer. (Know that this does not work well if you visit different slides, but is the perfect setup for visiting different layers on one slide.) Go to the layer settings, and set each of them like this:
Then arrange the body of the layer so the menu isn't covered, and Bob's your uncle. One menu, one set of triggers, and using the built-in visited state. The learner can see which tab they have clicked, and click on the one they want next.
One other point. If you use a jump to this slide to return to the base layer, you have one problem. If the slide is set to return to initial state on revisit, the clicking on that tab will reset the audio, and the visited states. If it is set to return to saved state on revisit, then the current layer will still show. If either of those describes what you want, you're fine. What I think I would want is to close the showing layer, and see the base slide as it is. To do that, create a layer with nothing on it, set to hide other layers, and with a trigger that says "Hide this layer when the timeline starts on this layer". 0n the DCU information tab, instead of jumping, show that layer. It will close any other layer that is open, then close itself.
To be perfectly frank, there are some more glamorous ways to make the learner aware of what layers they have visited, but they involve quite a bit more work, and in the end look and function the same as the simple way.
2 Replies
It can be relatively simple. First, the built-in states, like Visited, have their triggers built-in, so if you create one of them, it functions without the need of any further action from you. In fact, if you write a trigger to perform that function (like "Set state to visited when clicked"), it will most likely conflict with the built-in trigger, producing strange, but seldom wonderful results.
The simplest way to show which layers are visited is to use the visited state of the buttons on the base layer. (Know that this does not work well if you visit different slides, but is the perfect setup for visiting different layers on one slide.) Go to the layer settings, and set each of them like this:
Then arrange the body of the layer so the menu isn't covered, and Bob's your uncle. One menu, one set of triggers, and using the built-in visited state. The learner can see which tab they have clicked, and click on the one they want next.
One other point. If you use a jump to this slide to return to the base layer, you have one problem. If the slide is set to return to initial state on revisit, the clicking on that tab will reset the audio, and the visited states. If it is set to return to saved state on revisit, then the current layer will still show. If either of those describes what you want, you're fine. What I think I would want is to close the showing layer, and see the base slide as it is. To do that, create a layer with nothing on it, set to hide other layers, and with a trigger that says "Hide this layer when the timeline starts on this layer". 0n the DCU information tab, instead of jumping, show that layer. It will close any other layer that is open, then close itself.
To be perfectly frank, there are some more glamorous ways to make the learner aware of what layers they have visited, but they involve quite a bit more work, and in the end look and function the same as the simple way.
Hi Walt. Thank you for your reply. I was afraid that rearranging would be the best option lol. Ironically, Bob is my uncle!!!
This discussion is closed. You can start a new discussion or contact Articulate Support.