Hide Next button until objects have been visited

Hey Adam! I'm happy to lend a hand! No need to pull any more hair out. 😁

I made a few changes in your file, and now the next button is disabled until all three layers have been viewed. Here's a summary of what I did:

1. Add this trigger: Change state of Next button to Disabled when timeline starts.
2. Add a "Done" state to each graph on the base layer.
3. Add a trigger on each graph: Change state of graph to Done when the mouse hovers over.
4. Add a trigger: Change state of Next button to Normal when state of all 3 graphs are "Done."

Check out those changes in your file, and let me know what you think!

Glad to hear it. Thanks for sharing that.

I'm trying to do something similar. I have a slide containing 5 buttons. Each button is associated with a layer that contains information for the learner as well as a trigger and state (e.g.: Button 1 --> show layer Information Data when user clicks... and when the learner clicks the state changes to visited). I am trying to keep the Next button hidden until the learner has "visited" each button but the logic I've created doesn't seem to be working. Any thoughts? 

Hey, Steph! It sounds like you want to enable the Next button when all of the layer buttons are Visited. I can help with that!

Try this:

1. Add a trigger: Change state of Next button to Disabled when the timeline starts on the current slide.
2. Be sure all 5 buttons have a Visited state. You do not need any triggers to change the state of the buttons to Visited.
3. Add a trigger: Change state of Next button to Normal when the state of all 5 buttons are Visited.

If you need extra help, I'd love to take a look at your file! You can share it publicly here, or send it to me privately by uploading it here. 

Hey again, Steph!

It looks like you replied via email, and your attachment didn't come through. 

Instead, click here to open the discussion. Then, click the gray Add Attachment button at the bottom of the reply window. Click Choose File, and select the file from your computer.

I'll be standing by!

Steph,

I know when you use the wizard that "State of..." is one of the options for the When part of the trigger, but it doesn't work. There is nothing to make it happen. States do not initiate triggers. They are very useful in conditions. This is a known bug that doesn't work if there are five or more triggers on a slide.

You need to tie the trigger that changes the state of the NEXT button so some action the user takes, such as clicking a button to close each layer. In that case the trigger would read:

Change state of Next button to Normal when user clicks (Close Layer Button) On Condition that state of Button 1 is visited, AND state of Button is visited, and etc.

If your slide is not set up that way, then you can tie the triggers to the 5 buttons themselves:

First - Show Layer 1 when User clicks Button 1

Second trigger for Button 1: Change state of Next button to Normal when user clicks Button 1 On Condition that state of Button 1 is visited, AND state of Button is visited, and etc.

Sorry -- not sure what happened. Here is the file!

Hi there, Steph!

The triggers in your screenshot look correct. The only oddity I noticed is the location of the "Change state of the Next button to Normal" trigger. That should be under the Slide Triggers heading. 

Check out this sample file I put together for you, and use that as a model for your file. Let me know if that helps! 

Hi Alyssa,

I noticed that too. The trigger sometimes automatically jumps to the bottom when I want to add a new one to Slide Triggers and I'm not sure why.

The file you sent me is exactly what I'm trying to achieve. Do you think part of the issue is that I have mine set up so the learner uses the Previous button to return to slide 1.4 Classifying Data in order to select each subsequent button?

Hi, Steph!

I don't think the Previous button trigger should affect the other triggers in any way. Mind if I take a look at your original Storyline file?

You can share it publicly here, or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.