Previous Slide Trigger
I have used buttons for next/previous links instead of using the default ones on the player. I have placed them on the master slide and applied the previous/next triggers to them. They function correctly when using just the buttons to navegate the lessons.
Here's the problem. When you select a slide from the menu, then click previous slide it doesn't go to the previous slide in numbered order it goes to the slide you were just on.
So, to break it down say you were clicking next until you're on page 5, then go to the menu and skip to slide 10, then click the previous button, you don't go to slide 9, you go back to slide 5. I don't want it to do this. Is there a way to stop it from functioning this way besides changing the next/previous buttons to go specifically to a slide. I only ask this because slide structure/layout design can change after you have created it and I don't want to have to go through and keep manually changing the buttons. I'd like to be able to do it from the master.
20 Replies
Hi Natashia and welcome to Heroes!
This is currently the expected behavior as it's returning you to the previously seen slide, not necessarily what would appear in linear order. If you'd like it to function in linear order you'll need to add that as a trigger for each slide - so that on slide 10 it'll have Jump to slide 9 as the previous trigger.
Hi Ashley,
Yeah I was hoping that wasn't the case, thank-you
Hi Natashia,
It wouldn't be the first feature request I've seen for different behavior - but I know that this is currently by design.
It may be the "desired behavior", but it's unfortunately very counter-intuitive and time-consuming to get around. If I have 50 slides, I need to hard code all of them to jump to the previous slide, just in case the user might use the menu to navigate instead of the regular navigation.
If "jump to next slide" follows the numerical order of slides by default, you would expect the "jump to previous slide" to do the opposite.
How about splitting the trigger into two different ones, like "jump to previous slide" and "jump to last-visited slide" ?
Hi JC! It sounds really frustrating to manually adjust the triggers on so many slides -- I can see how that would be time-consuming!
Thanks for your idea to split the trigger into two different behaviors, i.e. "jump to previous slide" and "jump to last-visited slide." I'll be sure our Product team sees this!
I hope it makes it into the next update, because that would solve a huge issue. If you navigate with the menu instead of the buttons, you can essentially lock yourself within the course.
Hi JC,
There are a lot of different factors that determine new features and a few steps our team will go through first, so you're unlikely to see this in the next update. We'll keep you posted here if there is more to share on this - and I appreciate you bringing this up!
We got the same request here.
What a time consuming task to trigger each slide when we have linear navigation! BTW I like the idea to split that in 2 different behaviors.
Where do I sign ? :-P
Appreciate you adding your insight, Marie-Pascale! We're continuously exploring new features, and customer input is extremely valuable in that process.
I'll share this conversation with our team, and feel free to share any additional thoughts with us here or through the feature request form! 🙂
Thanks, just filled my request based on JC Goyette tread. Can't to see the next features. Keep on the good work guys.
Same issue here, and I agree it's counter-intuitive for the learner!
I just sent a feature request, too!
Thanks, Carrie.
I've added this conversation and your official feature request to a report as we track this.
I wanted to share some information about how we manage these feature requests as that may be helpful.
Any news on whether this update is coming?
Hello, Jean-Christophe!
To help you plan, we don't have immediate plans to set the logic for a previous slide trigger.
We'll notify you if we make any changes that might help. Thank you for checking in!
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?
Hello, I just want to add my voice: I thought the behavior described by the staff was a bug, and I came here looking to fix it. I am dismayed that there doesn't appear to be an easy fix, and I'll have to hack a solution.
Please split functionality into "Jump to slide > Previous slide" and "Jump to slide > Previously viewed slide".
Just want to put my two cents in. I really like that the back button is a historical back button because I'm making non-linear modules and like the idea that a student can get back to where he was.
Understandably there is value to having a choice.
Otro voto para esta solicitud tan necesaria. Tengo recursos con muchas pantallas y es mucho trabajo replicar un botón en vez de utilizar una diapositiva maestra.