Forum Discussion
hiding next button until all layers viewed
I hope someone can help me. I've been going over this more times than I can count and can't figure out what is wrong. I have 2 slides in a presentation (excerpted here). For both, I want to hide the next button until all the layers are viewed. The first one works. The second one doesn't. I cannot figure out what is wrong with the second slide. Please help!
many thanks, heather
The problem lies within the trigger, where the 'When' condition is set to 'When the timeline starts.' It should be changed to 'When the timeline ends,' just like on the previous slide. However, even after making this adjustment, there may not be enough time for the learner to click all the buttons before the timeline ends. If the timeline ends before all buttons are clicked or visited, the conditions will not be met, causing the next button to remain hidden. To fix this, you may consider extending the timeline to give learners more time to click all the buttons, although they still may not have enough time to read all the content revealed by clicking the buttons. At this point, I would recommend considering a different approach altogether.
Consider this trigger:
Additionally, all triggers that change the button state from Normal to Visited when clicked are redundant. When an object has a Visited built-in state, it will automatically switch to that state when the learner clicks it, so these triggers are unnecessary. I strongly recommend checking out the post PRIMER: Take advantage of built-in states by JudyNollet for a more comprehensive and detailed explanation of how built-in states work in Storyline.
The problem lies within the trigger, where the 'When' condition is set to 'When the timeline starts.' It should be changed to 'When the timeline ends,' just like on the previous slide. However, even after making this adjustment, there may not be enough time for the learner to click all the buttons before the timeline ends. If the timeline ends before all buttons are clicked or visited, the conditions will not be met, causing the next button to remain hidden. To fix this, you may consider extending the timeline to give learners more time to click all the buttons, although they still may not have enough time to read all the content revealed by clicking the buttons. At this point, I would recommend considering a different approach altogether.
Consider this trigger:
Additionally, all triggers that change the button state from Normal to Visited when clicked are redundant. When an object has a Visited built-in state, it will automatically switch to that state when the learner clicks it, so these triggers are unnecessary. I strongly recommend checking out the post PRIMER: Take advantage of built-in states by JudyNollet for a more comprehensive and detailed explanation of how built-in states work in Storyline.
Thank you so much. Your example is a much more elegant solution! I will also check out that Primer.
Here's another post you might find useful. The file demonstrates ways to control the Next button and explains the triggers. TIP: Controlling the NEXT Button 101 | Articulate - Community
