Custom "back" button w/ variable dependant triggers

Nov 23, 2013

This is one of those "nice to have" features that I haven't had too much time to play around with that I'm wondering if anyone else has figured out.

We use our own "player", per se, with our own forward/back buttons.  Our courses are also non-linear optional.  Learners always have the options to jump around but could take the course in a linear fashion if they choose.

If they go linear, the back button is a breeze. (I just always tell it to go to the previous slide)  However, if they jump around, I haven't figured out how to get them back to where they just were using the back button.  If, for example, I have 5 sections, they complete 1 and 2, skip 3 and go to 4.  when they're in section 4, they hit the back button, it's going to take them to 3, not 2.

Has anyone figured out a variable formula that creates this functionality?

If this is all too confusing, let me know and I'll throw together a quick Storyline file.

3 Replies
Mark Cairns

Hey Kevin,

I've run into that as well. I think storyline uses it's internal bookmarking to determine the "Previous Slide" state.

If you don't have a massive number of slides you could use a custom variable (in this case "CurrentSlide") to determine which slide your on then jump to slide based on the variable number. 

I've attached an example. (Most of the triggers happen on the slide master.)

Let me know if that works or if you've come up with a better way. (there must be a better way)



Ashley Terwilliger-Pollard

Thanks Mark for helping Kevin out here! Kevin, I can't think of an example that does what you're describing, as it'll be dependent on the path they take - which could be different for each user. Have you thought about using a menu slide? So that instead of directing the user back to the previous "scene" in the linear set up, that the back button always would take them to a menu where it would indicate those sections that have been visited (say using a button for each scene and the "visited" state)? 

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