Articulate NEXT button won't enable
Mar 11, 2021
Hi,
I have a slide "A" where I require users to go through all the slides linked to "A" before proceeding.
I placed objects in "A" which acts as hyperlinks to the linked slides. Objects will change state to "visited" after user returns from linked slides.
I followed the steps listed in https://articulate.com/support/article/how-to-temporarily-disable-or-hide-navigation-buttons. The problem is the NEXT button did not become "enable" after all the slides were visited.
I'm using Articulate SL 360
3 Replies
In this type of situation, you have to ensure that the trigger to enable NEXT will execute when the user returns to the slide. The best way to do that is with variables and conditions.
This post provides the instructions you need:
https://community.articulate.com/discussions/building-better-courses/create-a-custom-menu-slide
If you scroll down in the comments, you'll also find a file that demonstrates how this works.
Hi Judy,
I did what you suggested. Disable NEXT at the start and enable it after all required slides were visited. I added variable for the main slide and conditional triggers for the variable at the required slides. However, new problem. When I visited 1 slide, all the other slides became visited.
You've got triggers to change the ovals to Visited based on the mindsetofcoach variable. So as soon as that variable is adjusted to True, the ovals will become Visited when the timeline starts (as per the triggers).
As per the instructions in the link I provided, you should use a separate variable to track completion of each topic. You have 4 topics, so you'll need 4 variables.
Also, you don't need triggers to change the state of the clickable objects to Visited. When any object has a Visited state, it will automatically change to Visited when the user clicks it. That programming is built into Storyline.