Forum Discussion
State of Next Button
- 8 months ago
PoojaDwivedi-4d : Restricted navigation controls the Player's Next button. It doesn't affect custom buttons. (There's more info about controlling the Next button here: TIP: Controlling the NEXT Button 101 | Articulate - Community )
It sounds like you have a trigger that disables a custom next button when the timeline starts. That trigger will run every time the user returns to the slide. To prevent that from happening, add a condition (or conditions) to the trigger.
For example, suppose the trigger that enables the custom next button runs when the state of the buttons in the interaction are Visited.
In that case, the trigger that disables the custom next button could have conditions that check whether any of those buttons ≠ Visited. Here's an example:
PoojaDwivedi-4d : Restricted navigation controls the Player's Next button. It doesn't affect custom buttons. (There's more info about controlling the Next button here: TIP: Controlling the NEXT Button 101 | Articulate - Community )
It sounds like you have a trigger that disables a custom next button when the timeline starts. That trigger will run every time the user returns to the slide. To prevent that from happening, add a condition (or conditions) to the trigger.
For example, suppose the trigger that enables the custom next button runs when the state of the buttons in the interaction are Visited.
In that case, the trigger that disables the custom next button could have conditions that check whether any of those buttons ≠ Visited. Here's an example:
Related Content
- 2 years ago
- 5 months ago