\n
Do you want to create your own Menu slide? Do you want to ensure that the user can't advance to your summary and/or quiz until they have visited all of the other scenes in your course?
\n
Well, you're not alone. This topic comes up quite a bit in the community. Here are the basic instructions for creating a custom menu slide:
\n
\n- Create a T/F variable for each scene (topic, module, branch, or whatever you want to call it). Set the initial value be False to represent that the user hasn't yet completed the scene.
\n- On the last slide of each scene, create a trigger that adjusts the corresponding variable to True when the timeline starts or ends (depending on your preferred restrictions).\n
\n- Alternately, add the trigger to the Next button. But if you do that, be sure the trigger appears before the trigger that jumps to the next slide.
\n
\n \n- On the custom Menu slide, add a trigger to change the state of the Next button to Normal when the timeline starts.\n
\n- Include conditions so this trigger only executes if all of the variables = True. (Tip: To ensure all conditions are met before the trigger will run, connect the conditions with \"AND.\")
\n- Include an \"Else\" statement that changes Next to Disabled.
\n
\n \n
\n
\n
The attached a file demonstrates and explains how this works.
\n
By the way, you can use the same basic instructions even if you don't include the built-in Next button on your custom Menu slide.
\n
\n- To do that, use the steps above that describe how to disable and enable the Next button to disable and enable whatever button you have for advancing (for example, a Go to Quiz button).
\n
\n
\n
Variables and trigger conditions provide the real power in Storyline. If you're not familiar with them, I recommend that you check out these resources:
\n
\n
\n
UPDATE
\n
If you scroll down in the comments, Sarah Hodge's comment links to an example that shows how to make the user go through the scenes/sections in order.
\n
\n
Do you want to create your own Menu slide? Do you want to ensure that the user can't advance to your summary and/or quiz until they have visited all of the other scenes in your course?
\n
Well, you're not alone. This topic comes up quite a bit in the community. Here are the basic instructions for creating a custom menu slide:
\n
\n- Create a T/F variable for each scene (topic, module, branch, or whatever you want to call it). Set the initial value be False to represent that the user hasn't yet completed the scene.
\n- On the last slide of each scene, create a trigger that adjusts the corresponding variable to True when the timeline starts or ends (depending on your preferred restrictions).\n
\n- Alternately, add the trigger to the Next button. But if you do that, be sure the trigger appears before the trigger that jumps to the next slide.
\n
\n \n- On the custom Menu slide, add a trigger to change the state of the Next button to Normal when the timeline starts.\n
\n- Include conditions so this trigger only executes if all of the variables = True. (Tip: To ensure all conditions are met before the trigger will run, connect the conditions with \"AND.\")
\n- Include an \"Else\" statement that changes Next to Disabled.
\n
\n \n
\n
\n
The attached a file demonstrates and explains how this works.
\n
By the way, you can use the same basic instructions even if you don't include the built-in Next button on your custom Menu slide.
\n
\n- To do that, use the steps above that describe how to disable and enable the Next button to disable and enable whatever button you have for advancing (for example, a Go to Quiz button).
\n
\n
\n
Variables and trigger conditions provide the real power in Storyline. If you're not familiar with them, I recommend that you check out these resources:
\n
\n
\n
UPDATE
\n
If you scroll down in the comments, Sarah Hodge's comment links to an example that shows how to make the user go through the scenes/sections in order.
\n
Worked well! Thanks so much for the info.
Worked well! Thanks so much for the info.
