Hello! I have searched the Articulate tutorials looking for an answer to what I thought was a simple question: how do you prevent the "next" button from appearing until after all elements on the page have been looked at? In other words, I don't want the reader to advance until they've clicked on everything. Thanks in advance.
Here is a sample that illustrates several best practices in e-learning.
Opinions are strong and varied as to whether it is best to hide the NEXT button, or just disable it. Choose your own preference. For me, that argument is just one among many reasons to prefer building my own navigation.
Equally, there is a fair amount of support for using states, rather than triggers to indicate that everything has been clicked. It is a shortcut that sometimes can work, especially if the user doesn't leave this main page. Again, opinions vary, and some of us have found that complex navigation sometimes overwhelms states. On the other hand, there is no debate that variables can be changed only at the behest of you the designer, and are absolutely reliable.
In short, here is one among many ways to do what you want.
3 Replies
Hi Rick
assuming here you are using SL2, SL3 or SL360, you can use triggers:
Change state of Next button to (hidden or disabled) when timeline starts on your slide xx.
Change state of Next button to normal when (insert the action you want to happen)
Here is a sample that illustrates several best practices in e-learning.
Opinions are strong and varied as to whether it is best to hide the NEXT button, or just disable it. Choose your own preference. For me, that argument is just one among many reasons to prefer building my own navigation.
Equally, there is a fair amount of support for using states, rather than triggers to indicate that everything has been clicked. It is a shortcut that sometimes can work, especially if the user doesn't leave this main page. Again, opinions vary, and some of us have found that complex navigation sometimes overwhelms states. On the other hand, there is no debate that variables can be changed only at the behest of you the designer, and are absolutely reliable.
In short, here is one among many ways to do what you want.
Thanks everyone!
This discussion is closed. You can start a new discussion or contact Articulate Support.