Forum Discussion
Lock the "next" button until timeline ends
In Storyline 2, is there a way to 'lock' the next slide button so that it's not clickable until the slide ends? I found a thread from 3 years ago but am hoping a fix is in the newest version to avoid adding triggers to each slide.
Is there a setting I can change somewhere to cover all slides? I don't want to remove the button all together because then I'd have to have each slide auto advance, which I also do not want. I want the learner to have to click next to go to the next slide, but not to be able to just speed through the course by hitting the next button repeatedly.
- WaltHamiltonSuper Hero
Go into the player, and set the menu to restricted. That globally disables the NEXT button until the timeline finishes.
- DanielSposato1Community Member
You would then also have to set the seekbar to be read only as well or the user could just use that to skip through.
Hi Edina,
Valid question - as I could see how that would be the thought, but using the locked/restricted navigation does not change the way the next button will appear within the player. You can disable it manually as you said - but that's a slide by slide set up you'd need to implement. Definitely could be taxing if you've got a lot of slides though - so an idea and use case to share with our team as a feature request!
- MayaMichielsenCommunity Member
Hi, I work with two players (2 languages) and in one player the next button works like it should, but in the other player, the next button appears gray and is unclickable until the timeline end, I do not want this, but I can nog seem to find where the differences lay. It is a copy of a course with a different player, so the problem is the player... Can you help?
- EdianaCommunity Member
Thank you Ashley – I appreciate the prompt response. Seems like that will make it two feature requests – one for the Menu Options and another for global triggers. Would be great to apply a trigger globally rather than having to cut and paste to every slide.
- DanielSposato1Community Member
If you have a custom button you can show it only at the end using the timeline. But if you want to hide the built-in navigation you need to use 2 triggers. One to hide or disable the button and the other to set it back to normal.
- marieirelandCommunity Member
Thank you both - this is working perfectly!
- EdianaCommunity Member
Should the NEXT button be "Visibly" disabled when the Menu Option is set to 'Restricted'?
Similarly, should the "Next and Prev" button be "visibly" disabled (grayed out) when the Menu Options is set to Locked?
I know how to visibly disable using states and/or triggers but surprised that the Locked and Restricted functionalities in Menu Options does not do this automatically. Or, does it and it's just not working that way at my end? Anyone?
The more we know what types of features you need to be an effective course developer the better! So send along anything you think of or reach out here in the forums.
- SandeshNirulkarCommunity Member
How can I achieve this with custom next button?, Please help me with this. I designed back & next button inside the slide master.
Hi Sandesh!
Try adding a shape that matches the slide background on top of the custom next button to hide it until the timeline ends. Let me know if that's what you had in mind!
- SandeshNirulkarCommunity Member
Hi Alyssa!
*Thanks for the quick reply, for now, I have created both back and next
buttons on the main screen only and manage to complete the assignment, as
per your solution there is again we have to work on each slide, and
workload increases even after we are using slide master. but there should
be a solution that will help us in this case.*
- JenniferRoy-AsaCommunity Member
Hi, this thread is a couple years old and I am trying to accomplish the same thing. I need to prevent the user from racing through the slides so I'd like to fix the length of time of each slide before they can press Next (I don't want it to auto-advance). Have there been any improvements to make this easier? What's the best way to go about this?