Show state as visited when user can visit in no particular order

Hi!  I have a list of buttons the user should visit (not mandatory) and the user can visit them in no particular order.  This is so they only visit the buttons they need to.  I would like to show that when they click a button, a check mark appears to show them they have already visited that button.  However, since they can visit any or all and in any order, how do I do this?  The stumper here for me is that they can visit in any order. 


Thanks for any ideas?!

5 Replies
David Schwartz

Hi Becky,

Really simple way to do this is to add a checkmark to the Visited state of your buttons. 

There's some good information here:

Basically, though, go to States, chose a button and then click Edit States. Click the Visited state, and then with it selected, you can add an a shape, an icon, basically almost any element to that state, and position and size the element where you want it relative to the button itself. In the attached example, I just added a checkmark icon, colored it and sized it before moving it onto a corner of the button in the Visited state.

You can also do this kind of work with variables and triggers, but for your current use, it sounds like the built-in Visited state might be all you need.


Tobias Noeske

Another way to mark chapters as read is using triggers and variables. I liek to have my checkmarks or other completion markers independent from the visited state. This gives me more control over when exactly the chapter is marked as visited/completed.

I usually place the marker next to the button for the respective chapter and set the initial state to "Hidden". Once the user has reached the desired point (e.g. completed a quiz or reaches the last slide of a chapter) I will change a true/false variable for this chapter. Upon returning to the Table of contents slide a trigger will check the variable and then change the state of the respective completion marker to visible (if the completion criteria have been met).

David Schwartz


Completely agree, that's a much more elegant way to do it. What I don't like about the Visited state approach is that the learner sees the checkmark as soon as they click the button, and before they go to the clicked location.

A hybrid approach I sometimes take is to create a custom state for the button with the checkmark within it, and then use the same T/F variable you mention to set the appropriate state for the button itself.