Re: Problem with Menu States

Visited is a built-in state. Any object with a Visited state will automatically change to Visited when it is clicked. Adding a trigger that duplicates that action usually causes problems. 

• Because this happens automatically, it's better to change the buttons to a custom state based on the value of the variables. There's more info in this post: TIP: Create a Custom Menu Slide - Articulate Storyline Discussions - E-Learning Heroes 

I assume that your first trigger is supposed to change an inactivated (that is, Disabled) button to Normal after the user completes the previous section. However, this trigger will run every time the user returns to the slide. So even though a button may have been changed to another state, this trigger will change it back to Normal. 

• To prevent changing the button back to Normal, add another trigger that checks whether the corresponding section has been completed. So it would look something like this: 

That example comes from the download available in this post about creating a locked custom menu: Storyline 360: Custom Locked Menu - Downloads - E-Learning Heroes (articulate.com)