I would like your assistance in my current challenge.
I have disabled the "Continue" button in my first slide. In order for it to activate the learner needs to complete viewing three scenarios and answer the question as required. However when I tested the scene the "Continue" button does not allow me to move to the required next slide. I have tried all possible ways to complete viewing the scenarios (in order, backwards, out of sequence).
Please help me find a solution to my dilemma.
I have attached the file so you may get a better understanding of my challenge.
Look to the very trigger in your first slide's timeline. You'll see "unassigned" as the variable being checked. You need to watch an existing project variable (of boolean) as watches to "unassigned" never equal true
Thanks for including your file here. You don't actually need a variable for this, since each menu item jumps to a new slide. Instead, use this trigger which is based on states rather than a variable:
I made that change in your file and attached it here. Take a look, and let me know what you think!
I seem to be having the same trouble. I've tried removing the built in Next button altogether and simply having a "continue button" unhide when both article buttons are visited. That worked once and then simply stopped working...can't get it back. This is actually what I prefer but when it I couldn't get it, I went to using the built in Next button in the same manner. During preview, it worked once and then stopped working. I'm stumped! I'm sure it is something obvious I'm missing. Please take a look at my attachment.
Thanks for sharing your file and letting us take a look. I tested it out and saw that you'd included triggers for those two article buttons to change the state to Hover and Visited and that seems to be interfering with how the course behaves. Since those states are built-in there is no need to have triggers for them, as they'll behave as designed and described here. When you do add triggers to them, that can cause some odd, unintended behavior.
When I deleted those triggers, the next button appeared as you hoped when the state of both buttons were Visited.
7 Replies
Look to the very trigger in your first slide's timeline. You'll see "unassigned" as the variable being checked. You need to watch an existing project variable (of boolean) as watches to "unassigned" never equal true
Dear Brian,
I have tried assigning that trigger as well and still it didn't work.
Looking forward to your assistance.
Thank you.
Hi Sierry!
Thanks for including your file here. You don't actually need a variable for this, since each menu item jumps to a new slide. Instead, use this trigger which is based on states rather than a variable:
I made that change in your file and attached it here. Take a look, and let me know what you think!
Dear Alyssa,
You are a life saver. That worked really well. Thank you so much.
So glad that worked for you! Best of luck on the rest of your project. 😊
Alyssa,
I seem to be having the same trouble. I've tried removing the built in Next button altogether and simply having a "continue button" unhide when both article buttons are visited. That worked once and then simply stopped working...can't get it back. This is actually what I prefer but when it I couldn't get it, I went to using the built in Next button in the same manner. During preview, it worked once and then stopped working. I'm stumped! I'm sure it is something obvious I'm missing. Please take a look at my attachment.
Hi Becky,
Thanks for sharing your file and letting us take a look. I tested it out and saw that you'd included triggers for those two article buttons to change the state to Hover and Visited and that seems to be interfering with how the course behaves. Since those states are built-in there is no need to have triggers for them, as they'll behave as designed and described here. When you do add triggers to them, that can cause some odd, unintended behavior.
When I deleted those triggers, the next button appeared as you hoped when the state of both buttons were Visited.
This discussion is closed. You can start a new discussion or contact Articulate Support.