Previous Slide Trigger

A linear back button action in the jump to slide has been a long requested feature to allow for navigating linearly through the menu order would be great. A built-in variable to clear the previous history would suffice and probably be easier for your programmers to implement.

A built-in "ClearPreviousHistory" variable (true|false) would reset the previous navigation array to reflect the menu (or story view) up to the current slide. This would allow us to put navigation buttons in the master slides and conditionally reset the previous button with the "ClearPreviousHistory" at the beginning of a slide. This would be my preferred method as it would be easier to adapt old projects and retain previous button function conditionally.

I've also submitted this as a request.

Katie, could you please ONCE listen to your community? :) This thread goes round and round since the first iteration of Storyline. Every once a while someone complains, that prev/next triggers are not logical. You give as hierarchical view, the slides nicely connects in storyline line one-by-one, and then, after publishing, magic happens and we are bound to hardcode every navigation button in course if we have menu enabled... That's so, so irrational and you never try to even talk about that. For you, things are just like they are and you don't give a single about what people are telling you. 

Come on, that's not some ugly thing to change. If 'next' works as intended, changing prev to work as people think it should work, shouldn't be so troublesome. We are here, we are telling you, that actual way is wrong, and you just pop and says 'nah, we don't see a problem' - why are you treating people who are paying you such a big cash for your product like their voice doesn't matter?

No, I won't submit feature request, because that requests doesn't work. Do a proper voting for features and bugtracker to be in touch with your community and take some priority! We don't need 3d graphics inside, when storyline is full of bugs and no one listens... Who is in charge there obviously ignoring community voice?

Agreed, Jean-Christophe, but I personally can see a functional purpose for BOTH scenarios.

For example, someone is sitting on slide 25 and might want to quickly review something in an earlier slide so they click on a menu item which jumps them maybe 20 slides earlier. Once they have finished reviewing that slide they might want to immediately return to where they were, but if they press the back button and they are taken only 1 slide behind where they are now, it may be hard for them to get back to where they came from (except by using another menu item again, maybe).

I'd like to have BOTH options available to me (and to the learner) so they can either press a back button (moves linearly back by 1 slide) or they can press a return/previous button to go back to where they last were.

Acrobat provides BOTH navigation methods and I use them both - regularly.

Hi Julie!

Thanks for checking in on this!

I don't have any updates to share at this time as our team has been prioritizing other features, but I've included your voice in the feature report and will update this discussion if it makes it onto our Feature Roadmap!

For your reference, here's a closer look at how we manage feature requests.

Hi Jean-Christophe!

Thanks for reaching out!

I don't have any news to share at the moment, but we've included your voice in the feature request. We'll be sure to notify you if it makes it to our Feature Roadmap.

Have a great rest of your week!