Disabled NEXT button battles the PREVIOUS and loses! : )

Aug 04, 2016

I am working with SL2 (version 10) and have been disabling the NEXT button when slides have layers. I have a trigger that enables the NEXT button once all layer buttons are “visited”.

I have the slide properties set to "Resume Saved State"  hoping that all layers will maintain their "Visited" state so that the NEXT button will be enabled.

I’m noticing that if someone moves on to the next screen and decides to go back to the PREVIOUS screen….they need to click through all the layer buttons TWICE before the NEXT button is enabled again.

Is there a workaround for this that you can suggest?



10 Replies
Christie Pollick

Hi, Kelli -- Thanks so much for reaching out here and sorry for your troubles! If you were able to share your file, perhaps others would be able to take a look at how things are currently set and offer some suggestions to assist you further. Please use the grey ADD ATTACHMENT button in the bottom left of the reply box and you can browse/upload from there.

Wendy Farmer

As Christie said can you upload your file might be easier for someone to help you if they can work with your setup - everyone does things different, maybe it's trigger order - I can't say, I was just giving you an option for enabling the next button.

Resume saved state is a slide property for the objects on the screen not the player buttons. If you notice the triggers for Next and Previous are player triggers.

Wendy Farmer

Hi Kelli 

I just worked on slide 1 of your file.  I changed the trigger that enables Next to normal to 'when timeline starts' and used the button visited states in the condition.

I then added a trigger to the last layer - tab 4 that changes the Next button to normal when the timeline starts on that layer. Not knowing if you have audio on that slide or other objects that the user will interact with, but you could change that trigger on the layer to when media completes or uses clicks.

If you suspect the user will access the tab's out of order, then you would need to copy that trigger from layer 4 onto the other layers and include the button states in the condition or use variables to control it.

The inbuilt 'visited' state occurs when the user clicks on the tab - I usually create a custom state called completed and this allows me a little more control as I change the state of the button to visited when the layer starts for that tab.

Hope this helps.


Kelli Porcaro

hey thanks so much! But WOW! I have a lot of slides where this is a problem. So i'll have to add  the custom trigger to all of them.

But I'm curious, when you looked at the example I uploaded....why doesn't the Resume Saved State work for this? I thought the Resume State would eliminate the need to create another trigger. Just curious.

And thank you thank you!!

Emily Ruby

Hi Kelli,

I just wanted to clarify why the next button goes back to disabled. Since the next buttons are set to be disabled at the start of the slide, via trigger,  when returning to the slide the command we’ve given Storyline is to hide the buttons as soon as the slide starts. This will occur regardless of slide properties as the slide is restarting.

This is where adding conditions to that trigger come into play. You can set it up as Wendy shared, or add a t/f variable to each slide set to change to T on clicking next button, then add a condition to the disable trigger to only disable if that variable is False. Attached is an example.

Let me know if you need anything else.

This discussion is closed. You can start a new discussion or contact Articulate Support.