Hide/inactive the next button

John,

You can put a condition on the Next button trigger.

This doesn't hide the next button, but it does inactivate it.

Hi Meryem, i am new to Storyline, can you provide a bit more info?

thanks

John

See if this gives the detail you need:

http://www.articulate.com/support/storyline/how-to-disable-the-next-button-until-users-finish-interacting-with-a-slide

Hi Meryem,
I have found the solution. Thanks

http://en-au.articulate.com/support/storyline/how-to-disable-the-next-button-until-users-finish-interacting-with-a-slide

John

Is there going to be a simple way to do this across the entire presentation without having to build our own variables and conditions? It would be a really useful feature to have as an option for the Next button, always. I'll submit a feature request unless it's already on the "We're definitely doing this next update!" list :)

Hi Ashley! I'd always advise a feature request for things on your wish list :)

Hi Ashley - 

There's a way to do it without variables that's pretty easy to setup. See the attached example. This assumes you are using Storyline 2. 

• On the master slide, create a trigger to set the state of the Next button to disabled when the timeline starts.
• On your template slide (I usually setup templates for all of my slides that are copy / paste "stamps") add a shape called "unlock" or something similar. Move this shape to the end of your timeline. On timeline unlocks, I usually recommend going 4 seconds or so - just enough to prevent jackhammering the next button but not enough to cause tears of pain.
• Create a base timeline trigger to change the state of the next button to normal when the state of unlock changes to normal. This will activate the next button whenever this shape appears and by whatever mechanism that the button is activated.
• For timeline stuff, no further actions are required. If the timeline is set to resume saved state, everything will be as you left it. Resetting to initial state will cause everything to go back to the original slide entry.
• For interaction stuff, create another trigger that listens to state changes and set this up to turn on the unlock shape (hidden by default) when the state of X are all Y (all buttons are visited, for example). This cascades your logic and makes everything work nicely without variables. 

Pretty easy to setup and this can provide some really neat pivots for interactions (multiple cascading "unlocks" for groups of interactions)