I have a slide with the next button disabled, the slide contains 3 layers which once all 3 have been visited the next button needs to be enabled. What trigger should I be setting up to allow this to happen?
Next Button only shows up in the trigger wizard for slides that have a next Button, and you can't animate it in like a custom button.
FWIW: Best Practices
Plan A: Custom buttons
Plan B: Hide Next Button
Plan C: Disable Next Button
A lot of SL developers are forced to adopt Plan C (even though it creates user frustration), because Articulate hasn't yet figured out how to keep the Previous button in its place. When Next is hidden and Previous is not, Previous slides over to Next's position, causing user confusion. Just one of many strong arguments for creating your own navigation.
6 Replies
Change state of (your next button) to normal when states (of 3 buttons that show your layers) are all visited
There are other ways but this is easiest as a starting point
Consider setting next to hidden then it will animate in rather than just not working
Hi Dom
I see how this works for a button you've created.
Can this also be done using the build-in next button from the slide navigation control?
If so how would this work because I don't see where I can change the state of that button?
Thanks
Peter
Next Button only shows up in the trigger wizard for slides that have a next Button, and you can't animate it in like a custom button.
FWIW: Best Practices
Plan A: Custom buttons
Plan B: Hide Next Button
Plan C: Disable Next Button
A lot of SL developers are forced to adopt Plan C (even though it creates user frustration), because Articulate hasn't yet figured out how to keep the Previous button in its place. When Next is hidden and Previous is not, Previous slides over to Next's position, causing user confusion. Just one of many strong arguments for creating your own navigation.
Check here:
https://articulate.com/support/article/how-to-disable-the-next-button-until-users-finish-interacting-with-a-slide
I agree with the user confusion, we tend to do everything with custom UI and navigation now as it gives more control on things
Thanks everyone. Much clearer now
Peter
This discussion is closed. You can start a new discussion or contact Articulate Support.