Is it possible to create a custom menu on a slide in SL2 where we branch out to sub-sections of a module and then once a learner completes that section they return back to this menu slide and the a green check mark is added next to the title that the learner just completed and then the next section on the menu activates (able to click) to view this next section?
We essentially want to lock down all the sections and want to create a branching like main menu vs. having a linear, click next to continue, module.
If you have any examples (screenshots or demos) or story files, please share!
Hi Jason, if you are familiar with variables this shouldn't be very hard to do, maybe a bit repetitive if there's a great number of items in the Menu slide.
If I understood your request well, I would do the following:
1) Create a single boolean variable for each section of your course, set by default to "False". This would act as a check that a particular section has been visited).
2) On the last slide of each section, I would put a trigger that turns the variable (ex. Section1_viewed) to true. In the menu slide I would put the links that you want to "lock" in Disabled state by default. You might want to slightly change the look of these links in the state (ex. greyed out) to make more clear that they are currently locked.*
3) In the Menu slide, I'll add a trigger that changes the state of the links to Normal state with the condition of the "check" variable (Section1_viewed) must be true.
4) Same goes for the green check mark: just put it in Hidden state by default then add a trigger that turns its state to Normal if Section1_viewed is true
5) Repeat for every section of the menu slide.
* I would fire this trigger when timeline reaches 0.50 or someting like that: for some reason, variable changes "when the timeline starts" may have some bug, at least in my experience.
It sounds like your instructions are exactly what I need, but I'm a bit new to variables so I'm not quite sure how to go about implementing them into my module.
Here is a sample that may help you. Remember variables are just a way for one part of the course to send a text message to another part to describe what the first part did. Otherwise, the slides can't communicate with each other.
Hi Ed - Hopefully Dario is still subscribed to the thread here. If you do not hear back soon, you are welcome to reach out to the user directly via the 'Contact Me' option on the user profile.
If you have a file started that you'd like the community to assist with, feel free to share here.
Ah, thank you so much! Walt, i was able to use your example and recreate in a dummy module i was playing with.
Honestly, I'm not quite sure what happened. My older modules used variables that i implemented, and now a couple years later I'm revisiting them with 360 and I'm not sure if maybe something changed. In any case, I'm going to take some time and play some more with variables to develop a greater understanding. I appreciate the super fast response! life saver!
5 Replies
Hi Jason, if you are familiar with variables this shouldn't be very hard to do, maybe a bit repetitive if there's a great number of items in the Menu slide.
If I understood your request well, I would do the following:
1) Create a single boolean variable for each section of your course, set by default to "False". This would act as a check that a particular section has been visited).
2) On the last slide of each section, I would put a trigger that turns the variable (ex. Section1_viewed) to true. In the menu slide I would put the links that you want to "lock" in Disabled state by default. You might want to slightly change the look of these links in the state (ex. greyed out) to make more clear that they are currently locked.*
3) In the Menu slide, I'll add a trigger that changes the state of the links to Normal state with the condition of the "check" variable (Section1_viewed) must be true.
4) Same goes for the green check mark: just put it in Hidden state by default then add a trigger that turns its state to Normal if Section1_viewed is true
5) Repeat for every section of the menu slide.
* I would fire this trigger when timeline reaches 0.50 or someting like that: for some reason, variable changes "when the timeline starts" may have some bug, at least in my experience.
Hi Dario,
It sounds like your instructions are exactly what I need, but I'm a bit new to variables so I'm not quite sure how to go about implementing them into my module.
Ed,
Here is a sample that may help you. Remember variables are just a way for one part of the course to send a text message to another part to describe what the first part did. Otherwise, the slides can't communicate with each other.
Hi Ed - Hopefully Dario is still subscribed to the thread here. If you do not hear back soon, you are welcome to reach out to the user directly via the 'Contact Me' option on the user profile.
If you have a file started that you'd like the community to assist with, feel free to share here.
Ah, thank you so much! Walt, i was able to use your example and recreate in a dummy module i was playing with.
Honestly, I'm not quite sure what happened. My older modules used variables that i implemented, and now a couple years later I'm revisiting them with 360 and I'm not sure if maybe something changed. In any case, I'm going to take some time and play some more with variables to develop a greater understanding. I appreciate the super fast response! life saver!
This discussion is closed. You can start a new discussion or contact Articulate Support.