Forum Discussion
Next Button Trigger on Button “Visited”
Hi all
I’m trying to set the state of Next Button to Disabled when the timeline of a slide starts and go to Normal when the learner has visited (clicked) each button on the slide. When I created these a year ago, I don’t remember the “Visited” trigger option was there but I see it now. I was able to get it working in the first slide (laptop) of the attached, but not the second (Do’s & Don’ts). The Next button is still appearing after a few seconds. I’m sure it is something I crafted a year ago, but I can’t reverse it.
What am I missing? Thanks for all you do here – I’ve learned a lot.
I don't see anything on the second slide that would enable the Next button after a few seconds. It's possible that the slide is corrupted. I suggest you create a new version to see if that fixes the problem.
Also, I noticed that the buttons on the 2nd slide don't have a Visited state. That needs to be fixed if you're going to check for that state.
Finally, the triggers that disable the Next button should have conditions to ensure that they don't run if the user revisits the slide after completing the interaction.
- Note that it's better to use "≠ Visited" (instead of "= Normal"). That's because all the standard states are built on Normal.
- Be sure to connect the conditions with "or" so that the trigger will run if any of the conditions is met.
For additional info: TIP: Controlling the NEXT Button 101 | Articulate - Community
Hi Jack!
The issue here is that your pictures don't have visited states, they only have Normal and Hover (Screenshot below). Once you add visited states to all the Do's/Don'ts, it should work as expected.
I don't see anything on the second slide that would enable the Next button after a few seconds. It's possible that the slide is corrupted. I suggest you create a new version to see if that fixes the problem.
Also, I noticed that the buttons on the 2nd slide don't have a Visited state. That needs to be fixed if you're going to check for that state.
Finally, the triggers that disable the Next button should have conditions to ensure that they don't run if the user revisits the slide after completing the interaction.
- Note that it's better to use "≠ Visited" (instead of "= Normal"). That's because all the standard states are built on Normal.
- Be sure to connect the conditions with "or" so that the trigger will run if any of the conditions is met.
For additional info: TIP: Controlling the NEXT Button 101 | Articulate - Community
Thanks very much!
