TIP: Controlling the NEXT Button 101

I wish there was an easier way for a common issue than all these variable and trigger mumbo-jumbo programming hoop jumping. My newbie welcome to storyline is not turning out to be a pleasant experience.

Flexibility in result demands a wide variety of methods. In other words, if Articulate could solve everything for us, our creativity would be severely limited. Or, as somebody said, "Great reward demands great investment."

That's why we get paid the big bucks.

This is a great bit of info. I appreciate you building this and explaining the triggers and variables. 

Great! Thank you for sharing.

I so hope someone else will take up my issue that can offer a more inspiring and helpful answer.

Judy,

I can’t thank you enough for putting this information together into a Storyline file and making it available to everyone! I’ve only been working with Storyline for around 9 months and I’ve been pulling my hair out trying to troubleshoot the courses I’ve made (and the ones I didn’t make but I’m now responsible for making sure they work) when learners get stuck when they try to replay or go back to a slide they’ve already seen. I wish I didn’t have to restrict navigation because I know the science behind letting learners explore, but that aspect is out of my hands when it comes to my employer. 

Thank you so much for this, and I feel that you’ve saved me many hours of frustration!

Hi Judy,

Some really helpful content there, thanks for sharing!

I'm having a bit of trouble with slide attached. I was hoping you could offer a solution.

I've got 3 buttons, 2 set to disabled until the first has been visited and the subsequent layers seen.
I have a variable that says whether or not the 1st button has been set to T/F based on whether it's visited or not.
And I'm trying to make it so that Button 2's state turns to Normal once one of the 3 'answer' layers have been shown i.e. once the variable changes to True and the final layer in that trigger sequence has been seen and closed.

No matter what I try, it doesn't work properly. I have to go through the layers shown from clicking button 1, then once back on the base layer, have to click Button 1 again for Button 2's state to change. I've tried when the cursor hovers over the page, but that requires the cursor leaving the page and then returning. I've tried quite a few things but no luck!

Hoping you can help!!

Or am I trying to do something I needn't bother trying? Would it be better to cover the whole layer with semi-transparent colour, and just have a trigger saying 'change state of button 2 when button 1 is visited' - omitting variables altogether?

Hi, Glenn,

The attached file shows a simplified way to present each character's content, using only 1 layer per character.

The trick? Using states for the Feedback, which is controlled by a text variable. And enabling the next character button is done with a simple trigger on the layer's Close button. 

After the edited slide, I added a slide with some additional notes. 

Since this isn't directly related to the topic of this post, I suggest you start a new discussion if you have additional questions about your interaction. That'll make it easier for others to find in the future when searching. Also, a new post will probably be answered more quickly. (FYI: The Forum doesn't tag people. Someone will only get a notification if they subscribe to a discussion. So even a post's author won't necessarily get notified when a comment is added.) 

You all earn your "heroes" designation every single day. Thank you for saving me, yet again.

Thank you, Judy! Joining the chorus of gratitude to you for this extremely clear and helpful tutorial. I really appreciate you!