Forum Discussion
Disable Next Button on a Slide until all Buttons are Visited
This example illustrates how to disable next button when the timeline starts and enable next button when a variable change occurs after all of the slide buttons/objects have a state change to visited.
Note: All buttons must have a visited state. The next button will be enabled if the slide is revisited.
Step 1:
Create a True/False variable for the slide objects visited (SlideNumb_Action_VariableType).
Example Variable:
Variable Name, Type = True/false, Default Value = False
S1_AllObjectsVisited_TF
Step 2:
Create a trigger that changes the next button to disabled when the timeline starts if the variable is not equal to true.
Example Trigger:
Step 3:
Adjust the variable when the identified slide elements change to a visited state.
Example Trigger:
Step 4:
Change the state of the next button to normal when variable changes.
Example Trigger:
Thanks James for sharing those steps here! Sounds similar to another example we've documented here for Storyline 2.
Hello. I've used triggers like in the example you posted, Ashley, to set the Next button to not appear until the timeline reaches the end. This seemed to work fine, but I recently found out that if you hit the Enter button, it advances the slide without having to click the Next button. Also, when viewing on a tablet, the user can just swipe ahead before the Next button appears. Is there a way to disable this functionality so the slide can only be advanced by clicking Next when the button appears? I have searched the forums everywhere and can find out how to do this? thanks.
Hello Jeremy and welcome to E-Learning Heroes :)
This is actually an open issue that our team is currently investigating:
Player navigation does not work as expected when you press spacebar or Enter key after the first slide if the Next Button is set to hidden when timeline starts
I'm going to add this conversation to the report as we track user impact and so that we can update you here when we can as well.
No known workaround is listed at this time.
Thank You Leslie! This is a major issue for us because some of our end users are paid for their time spent completing courses. Also, if they are able to repeatedly hit Enter and skip through an entire course in 2 minutes when it’s supposed to be a 45 minute course, it’s a compliance issue as well. Hopefully a workaround or setting that prevents users from skipping ahead will be added or included in a software update soon. I hope we don’t have to redesign all of our courses or go back to using Adobe Captivate because of this loophole. Currently using Storyline 360.
This is great; however, the problem I've had is that when the learner returns to the slide by clicking the Previous button, the Next button doesn't appear and they have to re-click all the buttons again to get it to re-display. I tried setting the slide properties to "Resume saved state," but it still doesn't work.
Hi Thomas!
I'm happy to investigate! Would you mind sharing your file so that we can see which triggers you've already created?
You can do so by using the "add attachment" button in this discussion. Or you can share the file privately with our Support Engineers by using this link.
Thanks Lauren, but my work is highly proprietary and cannot be shared outside the company. I did manage a workaround that seems to work. Instead of hiding the Next button, I simply disabled it. It's not perfect as a disabled Next button displays. It passed SME review without anyone pointing it out, so I'm leaving it as is.
Dear Lauren,
I used the tips recommended but face a problem exactly like what thomas trampf described.
However, once I link those 5 navigation buttons out to another scene/slide, and learner returns to the slide by clicking the "Previous" button, the states of my button no longer stays visited.
As a result, the "Next" button doesn't appear even if learner has gone through all 5 scenes.
Pls advise. Thanks.
Hi Benedict
see if the attached works how you want
I followed these instructions on Storyline 3 and it worked. Thank you so much for posting!!!
I've tried following these instructions but the Next button is available after about 5 seconds regardless of variable value.
Are you leaving the slide with the buttons to go to other slides and then returning?
If so,
Triggers should be:
change state of next button to disabled when timeline starts on the slide with buttons.
change state of next button to normal when timeline starts on the slide with button on condition xyz is visited.
Use the Add Attachment button to attach your .story file, and let someone take a look at it.
Wow! Thanks for responding to my question Wendy.
My PC with SL3 software is in the office, I will check back on this when back office monday. But am so impressed by speed of your response, just have to say thank you again :)
