Forum Discussion
Next Button Trigger on Button “Visited”
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
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!