Forum Discussion
JudyNollet
10 months agoSuper Hero
You have these triggers on all of the rectangles/buttons:
- These triggers are redundant.
- You don't need "state of __ = Visited" conditions. The trigger already is set to run "When the state of all of the rectangles is Visited."
Each button also has a trigger to show a layer, and the layer leads to more content. On the layer, the base button's state is set to Hidden. That means all 4 buttons will never be in the Visited state at the same time.
Hiding the buttons also prevents the user from revisiting content. And the layers are only used to show a button to link to the associated module. That's unneeded clicking.
I suggest you do this:
- Have each button on the base jump directly to the associated module/scene.
- Add a Continue button to the slide that jumps to the Knowledge Check. Set its Initial State to Hidden. (Note: When you do this, the object will automatically be hidden until a trigger changes its state to Normal. You don't need a trigger to change it to Hidden.)
- Add a trigger that changes the state of the Continue button to Normal when the timeline start with conditions so this only happens after the scenes have been viewed.
- Those conditions could check that the buttons are all Visited.
- However, depending on how the course is set up, it might be possible for the user to return to the slide before they actually finish a module (for example, jumping to a module and then clicking the PREV button or using the built-in Menu). If that's the case, use variables to track completion of the scenes.
- This post describes how to create a custom menu slide that tracks whether a user has finished each section. It also includes a demo file. TIP: Create a Custom Menu Slide - Articulate Storyline Discussions - E-Learning Heroes