New user needs button help

May 30, 2013

I am attempting to provide 3 buttons branching off to 3 separate slide sets. Once all 3 are visited / learned the user can pass onto the next pathway of slides. How do I make a button function only once so the user will need to complete the set of slides and go back and select one of the other two buttons left.  Any help greatly appreciated. 


4 Replies
Christine Hendrickson

Welcome to E-Learning Heroes, Philip!

I've always loved this type of branching in courses and I've seen a few projects set up like this. However, it really depends on how you want to control those three buttons on your main slide/main section of the course.

First - Do you want to disable the branches after they've been viewed? It sounds like that may be the case.

Second - Do you want to have the users view the sections in a specific order? Or does the order not matter?

There's a few ways you can set this up, using variables and states - but it's difficult to give suggestions without knowing exactly how you envision this.

Do you have something already set up for the project? If you're able to share the .STORY file, I'd be happy to take a look and share some suggestions. I'm sure our community would be able to provide some tips and examples, as well :)

Thanks and welcome again, Phil!

Philip Landry

Hey Christine;

I was just thinking that the only way you could get to this "branch" of the STORY is by clicking that button which would take you back to the main 3 button slide at the end of the branch's progression. If the button was disabled after one use then the person would not be able to go down that road anymore as the access would be blocked. I dont care about the order that someone explores the branches.

Thanks for any help , it is greatly appreciated.


eTam Miller

Welcome Philip,

What you are describing is similar to how I set up my main menus , so I'll see if I can help.

First, I normally make a custom visited state, but that's optional since 'Visited' is built in. If you choose to do that you should make a visited state for each of your buttons before follwing these steps:

On your main menu (with the 3 buttons)

1. First, make sure all your buttons are in Normal state

2. On your main menu, create a true/false variable and name it anything you want

3. Choose 'False' as the initial value

4. At the end of each of your 3 sections, create a trigger on the final button that will lead the user back to the main menu. On this trigger:

a. Choose "Adjust variable"

b. Choose the variable you created

c. Choose "Operator=Assignment"

d. Choose "Value=Value;true"

e. Choose "When user clicks"

f. Choose "Continue button"

Make sure the trigger is on top

5. Back on your main menu, create another trigger. On this trigger:

a. Choose "Change state of" button or object

b. Choose "to Visited state"

c. Choose "When timeline Starts"

d. Create a condition- on the condition "if variables = = equal to value true"

6. On main menu, create a trigger that jumps to the next slide on the condition that all three buttons are Visited = true.

Hope this helps.

Christine Hendrickson

Hi Phil,

Great :) Thanks for the additional information.

You should definitely be able to set something up for this project. The first thing I want to mention is that you'll want to make sure that your revisiting setting for the main 3 button slide is set to "Resume saved state". I point this out because if you go off of states, and you don't use this setting, you may end up returning to the slide in its original state. This will make a pretty big impact on this type of project design. 

Here's a quick example I created:

Example for Phil - Sections

In the example I used states and triggers to "unlock" the final section button on the slide. 

First, I modified the "Disabled" states for the buttons so they'd appear complete after being used. Then I added a trigger to change the state of that button to "Disabled" when the user clicks - in addition to the "Jump To" trigger. 

I set the initial state for the final section's button to "Disabled". I added a trigger that will "unlock" that button and set its state to "Normal" when the state of all of  the other buttons are equal to "Disabled".

I'm also attaching the example, if you'd like to take a closer look.

Let me know if you have any trouble with this, or any questions.

Thanks Phil!

This discussion is closed. You can start a new discussion or contact Articulate Support.