Navigation through menu

There is a tutorial here that will help you set menu navigation to locked, which is what I think you want.

As to disabling the Next button, I don't have a tutorial, but here is a module that requires the user to view 4 different information sources, after which the Previous and Next buttons become visible.

I do not support, as some do, that you show the buttons, but disable them. I personally am very frustrated if I can see the Next button, but can't click on it.

Thank you, Walt. I really appreciate the help. I'm not sure I have the brainpower yet to absorb everything you did there as I'm only on my second Storyline project. I'll give it a try, though. And thanks for the tips on the menu. Much appreciated!

If you have any questions, just ask.

Hello Cheryl,

While I agree with Walt on the frustration one can get from clicking what seems to be a functional button but nothing happens, I think it can be minimized by creating a kind of prompt that explains why it doesn't take them anywhere yet.

In my case, I created a slide that I would use as a "lightbox" and can be shown from anywhere in the course. I made it appear similar to the prompt that appears when a quiz question is submitted without choosing anything. It has some text saying "You need to view all items before continuing the course." and a button saying "OK."

Example: Let's say I have a slide in my course that has 4 buttons that I want clicked before being allowed to continue.

First, I modified my Next button trigger with conditions to check that each button's state is equal to "visited". Be sure to choose "AND" for each button (btn1 = "visited" AND btn2 = "visited, etc.)

The I create another trigger on the Next button, to show my "show all" lightbox slide if any of my buttons state is not equal to "visited." In this case, be sure to choose "OR" (btn1 != "visited" OR btn2 != "visited", etc.)

You can copy those triggers and paste on any new slide that has multiple items you want clicked. Of course you'll have to then modify your conditions based on number and name of new buttons.

Hope that helps.

Thank you, Scott. I appreciate the additional input. It's been years (and years) since I did work like this in Authorware. I need some quiet time to test some of these out myself to really understand the logic. 

Thanks! 

No problem.

Also, I just remembered that if you are working with Storyline 2 you can set the state of the Next button to "Hidden" when the timeline starts. The create another trigger to change the state to "Visible" when all your button states are "Visited", similar to previous post.

My first post was a possible solution I've used in SL2.

Hi Cheryl,

To back up what Walt and Scott have shared here - you may also want to take a look at this article on disabling or hiding the next button.  

Hope that helps and best of luck with the rest of your project! 

Awesome! You all are so helpful. I really appreciate it. I bombed my second project and have to redo it. I need to lock some of these things down! Thanks again.