Forum Discussion
JudyNollet
3 years agoSuper Hero
Hi, Chris,
As Maria said, it confuses the program if you use triggers that duplicate what happens automatically. Built-in functionality will change an object with a Visited state to Visited as soon as the user clicks it. So don't use a trigger for that.
So, you've got a trigger to change the state of the Next button, but it isn't running. Here are the typical issues for that:
- The trigger appears after a trigger that jumps to another slide. That doesn't work, because the program can only run triggers on the slide it's on. This can be fixed by moving the trigger up.
- The "when" for the trigger isn't happening. How to fix this depends on how the slide is set up.
- Another issue with custom menu slides: The trigger to change the state of the Next button runs and the program jumps to the appropriate slide. But when the user returns, the trigger that disables the Next button runs again. This can be fixed by using a variable and trigger conditions.
This post provides more info and a demo file about the programming for custom menu slides:
https://community.articulate.com/discussions/building-better-courses/create-a-custom-menu-slide
This post provides more info and a demo file about different methods to control the Next button: