Graying out button when lesson is visited....

Feb 06, 2016

I have to be missing something simple, folks!? I have a slide master with a menu with buttons for navigation to all lessons in the course. Learners can display the menu on the screen from any point in the course and move to a new lesson.

I want a button to appear grayed out if a lesson has been visited. Should be a built in feature with a grayed out state for 'visited'....but it's not working and I can't figure out why??

1. There is a menu icon on the base layer of the slide master which displays on all screens. When that icon is clicked, a layer on the slide master is displayed with the buttons laying over the current screen.

2. Have made the buttons a set.

3. Have both a selected and visited state, each with a grayed-out icon.

4. There are no slides that 'reset to initial state.'

The perpetual menu works beautifully....but icons never appear grayed out.

What am I missing? Ideas please?

Thanks!

3 Replies
Steve Flowers

Hi Carrie - 

Couple of things. There is a built-in state called Disabled that will both show a disabled visual state and prevent clicking on the button. That's probably the state you want to use to disable navigation.

The other behavior with buttons on a Master slide is they are kind of "dumb", meaning they don't know what to do and won't remember state. To get around this, you'll need to use triggers and variables. 

Create a variable for each section (s1complete, s2complete, s3complete) you can make these whatever you want but it could be easier to use a true false variable with a default of false.

At the end of each section (or wherever you want to put it) use a trigger when the slide loads to change the correlating variable to true. 

Now back to your master slide. For each button, create a trigger:

When the timeline starts, change state of buttonX to disabled if sxComplete is true.

If you have 4 buttons, you'll have 4 triggers and 4 variables. Now when the master slide loads, it'll be "smart" and will know what to do! :)

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