how to make impossible going to next slide

Have a look at the attached file and see if that's what you want. I opted for using the Visited state of each menu button as the indicator for 'Completion' and added a layer that is displayed when the next button is clicked before all topics have been visited. Hope that helps.

I really like Michael's example for getting this done, very simple and elegant and easier to implement than using variables.

IF I were to use variables, however, I would create 8 variables all default to a value of False, and then set each variable to True when the section was visited. Your Next button would not be active unless ALL 8 variables equaled True.

With that being said, (again), I like Michael's solution of using the visited state of the buttons to control this

The down side of doing it that way is that if you can get back to the main page without reading all of the slides in any section, the state of that button will still move to "Visited"

I tend to create a state called "Completed" and put a tick into it and set it so you can move on after their states change to "Completed". I then create a variable for each section using True/False like Brian said, and set the variable to change when the timeline of the last slide in the section starts.

That way, when you move back to the main menu, there's a tick to tell you that you've completed that section, and it will only appear if you've visited all of the slides in that section.

C

Similar conversation going on here - http://community.articulate.com/forums/p/53548/286836.aspx

Yep, using variables instead of object states is another option to achieve the same result. I was only on my first cup of coffee, so using states was all my sluggish brain could come up with

I think we need a "like" button on here Michael, because I wanted to like that last statement!!

Haha, ditto here... And besides, using states can be a great solution for this. It's just with Storyline, as usual, there are at least 2 ways to do everything!

At least!! and different ones are better at different times!!

Thank you all for your prompt replies and your support.

I will test both solutions. Thanks again.

Btw. very nice design Etienne

Thanks, collective brain.  
With all of your help, I just figured out my similar issue (so ... thanks!)

I had 7 pins, each showed a layer, played the audio, closed the layer, and I wanted the "NEXT" button only to appear after all 7 had been visited.

Originally - I had the NEXT button on a layer, but that meant it prevented the last "pin" from playing, or the layer prevented the NEXT button from showing, depending on the order of my variables.

Here's how I got around it (with your help of course)

• Each "pin" has two triggers: change state of Pin1 to "visited" and show the applicable layer
• I set the Initial state of NEXT button to "hidden" on the base layer (that was my mistake previously - I had put the button on a new layer and it interfered with the other layers)
• Change state of "NEXT" to normal when Pin1 and Pin2 and Pin3 (etc) are "visited"

BOOM.  Works like a charm.

Ah, so great Scott! That's why we keep these older discussions around. I'm glad it helped you out.