A Choose Your Own Adventure navigation

This is the example I was trying to emulate. You can go in any order but when you go back to the main menu, the images states indicate they have already been visited. 

https://slidesugar.s3-us-west-1.amazonaws.com/howtofightabear/story_html5.html

Generally, the Visited state is pretty reliable for indicating layers that have been visited on the same slide; less so when visiting other (or groups of other) slides. In those cases, I use a trigger to set the state on revisiting the menu slide. But that can also cause problems if you create your own trigger to change a built-in state, because it conflicts with the built-in action. So I give the state a different name.

Most of us set a variable when each section is completed, and set the state when the timeline starts on the menu slide. Returning will start the timeline, and the trigger reads, "Change state of XXXX to Completed when timeline starts on this slide if {SectionVisitedVariable] = true.  Just rename the Visited state to Completed, and you're good to go.

There is a sample at this discussion:

You wrote:

When I tried to change the name of the state from visited to completed, it gave me the message "renaming a built-in state disables its default function"

That's precisely why you need to change the name. As long as that default function (Visited state)  exists, it is not totally reliable for what you need to do. But you can't just write the new triggers for it if it has the default name and thereby the default function. That can cause serious conflicts.

The menu has new triggers to change the objects to Completed state according to the the value of the variables. Then each of the three branches has a trigger to set the variable when the learner is finished with that scene.

Hi Folks, First time poster here! I have a similar/adjacent issue. I'm trying to get the objects to hold their visited state when returning to the main slide, from other slides. The first button (Health and Safety) works just fine. I copied it, to create Sustainability, and it won't hold the visited state unless you visit the object twice. I cannot figure out why one works and the other doesn't. Any help is appreciated. 

Thanks, 

Bethany,

I'm there. It was late when I finished that, and I didn't test it.  Sorry.

Set the initial value of AboutUs to False.

On slde 3.6, NOT QUITE layer, set the first trigger to Set CompanyCulture, instead of AboutUs.

Give that a try.

By the way, nice looking design.

Lindsay,

Sometimes things can happen when objects are copied. My first step would be to delete the second button, and recreate it from scratch. That sometimes straightens things out.

Here's your problem:

Once the Jump trigger is encountered, the jump starts, and all the rest of the triggers below it are forgotten. Set the variable before you jump, and all will be well.

I never thought that the trigger panel was like the timeline panel but that really makes sense. Things need to be in order. Been using SL for over a year and that's such a valuable lesson. 

I hope this thread can help others because it just opened up a door for me. These classes were going out for review today and I was going to have to dismantle the menu and make the class linear. 

Thanks for saving my class and sanity, Walt! 

You’re welcome, and don’t feel badly. This is such a common problem, it should be mentioned in the User Guide.