Disabling / re-enabling the player's Next button

Apr 21, 2015

I have a Storyline slide on which the user must click five checkboxes before the hidden Next button becomes visible. Clicking each checkbox will take the user to a different scene in the course; once they reach the end of the scene, clicking a "Home" button returns the user to the "landing page," where they can click the next box. Once the user has visited all of the scenes and all five checkboxes are clicked, the player's Next button should become visible, but it doesn't. The button appears briefly when the user clicks the last trigger, but then that trigger takes the user from the landing page to the appropriate scene; by the time the user returns to the landing page, the Next button is gone, even though all the checkboxes are selected.

In the end, I disabled the player's Next button on the landing page and created my own, making it initially hidden and then visible after all of the boxes are checked. This worked well, but aesthetically, I would have preferred to rely on the player's Next button.

Is there any way that I could have made this work without creating a new button?

Thanks in advance for your help.

2 Replies
Michael Shannon

Hey Dana. If I understand you challenge properly I may have a solution for you.

I've attached a story file that may help. I had a similar issue but for me it was lightboxes (similar but different solution to that one). For this solution you hide the next button and release it once each of your buttons are selected. Clicking a checkbox takes you to your page (or it could be a scene), once you are on that page/scene you trigger a true/false variable (to true in this case). Once you go back to the home page a trigger changes the checkbox to selected when the timeline starts if the accompanying variable is true. Once you visit all of the required pages another trigger kicks in on the home page: if all of the checkboxes are selected then show the next button. 

Let me know if you have any questions.


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