Changing State Of Image to Visited

Sep 15, 2016

Hi - I am using 4 photographs as a tracker for people to move through a course. So the learners click on a particular photo, it takes them to a module and then they return to the tracker. I want to change the state of the photo once it has been visited. Have set the state so that the photo is 40% transparent once visited.

If the photo was a button the state change would automatically happen, but as it is not a button, I think I need to set up a trigger to do this  - have tried a few options but can't figure it out....any ideas?

Alternatively - is there a way to format a button as a photo? Then state changes are automatically triggered.

Thanks!

8 Replies
Luke Benfield

There may be an easier way to do this, but for situations like these, I do the following that works every time:

- Create a True/False variable for each picture and set the default value to false.

- Pick where in each segment it would be appropriate to give the learner "credit" for viewing that content. Can be at the very beginning, or at the end. Create a trigger to adjust the variable for that segment to True. Do this for each segment's corresponding variable.

- Create a trigger for each photo on the photo slide with this format - change state of the photo to visited when the timeline starts with the condition of that photo's corresponding variable being equal to true.

Like I said, someone may have a simpler solution, but this one always works for me.

Walt Hamilton

Luke's suggestion is probably best, but do not name the state Visited, for two reasons.

Most importantly, when an object (any object, even pictures) has a state named Visited, the built-in trigger for visited is automatically triggered. If you are writing your own triggers, they may very well conflict, yielding sometimes spectacular, but seldom desirable results.

Also, if your user is visiting other slides, especially if the visit involves some branching, the original slide can easily become confused about what has been visited, and what hasn't. Using a variable to set the state when the timeline starts is as close to fool-proof as it gets.

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