Disabling Next button before proceeding to next slide

Oct 04, 2019

I'm wondering if anyone else is having issues when restricting the learner from advancing to the next slide until all items are visited on their current slide. My team has tried many different techniques to try and get this to work, but have been unsuccessful. We've tried the following;

1. Change the state of the Next button to disabled when timeline starts. Then change the state of the Next button to normal, on the condition that all icons are visited. (Note: this technique only works when the slides are light-boxed. If the learner navigates to a different slide or scene, this does not work and the Next button is still set to disabled).

2. Change the state of the Next button to disabled when timeline starts. There are three icons on the page so we added a number variable that would add a value of 1, when each icon is clicked.  Then, we added a trigger that would change the state of the Next button to Normal on the condition that the variable is greater than or equal to 3. (Note: the icons navigate to a light-box slide, and the value is not being added to the variable when clicked.)

3. Change the state of the Next button to disabled when the timeline starts. There are three icons on the page so we added a True/False variable (Default set to False), that would change the value to True when each icon is clicked. Then, we added a trigger that would change the state of the Next button to Normal on the condition that each icon is equal to True. (Note: the icons navigate to a light-box slide, and the value is not being changed to false when the icons are clicked)

*Please note that once each icon is clicked, a light-box slide pops up. We've also tried setting it to jump to a slide, or jump to a different scene but we always seem to run into the same issue no matter how we set up the triggers.

Has anyone else had trouble getting this feature to work? My team feels that this is one of many bugs within Articulate.

Can someone please help? :)

3 Replies
Randy Hill

This seems to be a common thread with some people today. I use disabled Next button states all the time with no issue of having it become available once buttons are clicked, no matter what they are showing. Do you by chance have a story file you could share of what your team is doing?

Are you using the built in states for the icons? What trigger are you using to change the next button? When time line starts (with conditions) or Change when states of? I tend to use both depending on the browser one or the other may fail. 

It sounds like you main issue is that your variable (true false variables would be best here) are not changing when the icon is pressed. That is where I would start looking.

Maureen Matsumoto

Hi Christopher,

Check out this post from today. It should resolve your issues.

https://community.articulate.com/discussions/articulate-storyline/using-variables-to-control-slide-advancement

There are a couple of different ways explained in the post to fix your problem.

Let me know if this doesn't solve your problem.

 

Ned Whiteley

Hi Christopher,

Your team were on the right track, but I suspect that the trigger order is incorrect.

In the attached example I have used True/False variables for when each button is clicked. I prefer this to a straight numeric variable as that doesn't prevent a user clicking the same button several times in order to advance. The important thing to see in this example is that, when you Lightbox to another slide before triggering a variable change, the variable change won't occur as the focus has already moved to the Lightbox slide. What you need to do is to change the variable first and then Lightbox to the new slide. I have demonstrated both options for the trigger order in the example and, as you will be able to see, one works and one doesn't.

Your final trigger to reveal the Next button should have conditions that each of the button variables (in the case of my example, Lightbox1Visited and Lightbox2Visited) are equal to True.

Hope this helps.

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