Forum Discussion

Gee1's avatar
Gee1
Community Member
5 months ago

Locked menu not working as expected

Hi community,

It's been about a year since I've interacted with this community due to being out of work. Now I'm back in the saddle and re-sharpening skills. 

I'm working on setting up a template for my team to work from, and the template uses a locked menu in the beginning of the course similar to this discussion thread How I Made This Custom Locked Menu in Storyline 360 | Articulate - Community

Maybe I need a fresh set of eyes, but for some reason my triggers are not working as expected. In particular, when the user clicks on menu item 1 (button 1) and completes section 1, upon returning to the main menu, the state of button 1 changes to "normal" and menu item 2 (button 2) changes from "disabled" to "normal", and so on, until the user completes all sections in order.

What I'm experiencing is, after button 2 is clicked, you can see it visibly change states from "normal" to "visited". But after the user completes the section, button 2 immediately changes back to the "normal" state from the "visited" state, which in turn, does not trigger button 3 to change states so the user can continue to the next section.

All buttons are set to "disabled" as their initial state, except the first button.  I've also set the "revisiting" properties to Resume saved state. I used the above article as reference to make sure I wasn't missing anything, but apparently I must be.

I can attach the SL file if necessary. 

 

Thanks in advance!

3 Replies

  • The description of the programming sounds like the buttons should work as described. Yet, as I understand it, button 2 returns to the Normal state when the user returns to the custom menu slide after completing that section. But it should be in the Visited state.

    Best guess: There's a trigger that changes the state of button 2 to Normal when the timeline starts on the slide, with the condition that button 1 = Visited. That condition is met, so the trigger runs again.

    FYI: A “when timeline starts” triggers runs every time the user reaches the slide—even if the Slide Properties are set to “Resume saved state.”  Therefore, if you don’t want the trigger to run in some situations, you need to add conditions to the trigger. 

    If that's not the problem, well, troubleshooting is just guessing without seeing all the programming. Someone might be able to solve the issue if you upload the .story file. Here are the best practices for doing that:

    • Only include slides that are related to the problem.
    • Be sure objects, layers, motion paths, and variables have meaningful names.
    • If there is proprietary content, replace or delete it. For example, replace proprietary text with “ipsum lorem” text.

     

    For custom menus, I think it's better to use T/F variables to track what's been completed. Here's more info about that option: TIP: Create a Custom Menu Slide | Articulate - Community 

  • Gee1's avatar
    Gee1
    Community Member

    Thanks for the responses. Well, while playing with the triggers and conditions, I noticed the option for button sets, which made it much simpler to create! As I now remember, that was a newly added feature at the time that I forgot about after being idle for a year! 

    Thanks for jogging my memory!