Jump to Slide [%%variable%%] AND Jump to Slide [the_one_before_this_one]
Jan 12, 2021
I've read questions from as far back as "the beginning" of Storyline that STILL have not been resolved.
Can any of you please help me find a reasonable answer to these 2 questions?
It has been nearly a DECADE, and we still cannot do 2 (simple) things that LOTS of us need.
1) Jump to a slide which is contained in a variable (If I put a 7 into a variable, then a trigger jumps to slide 7. If I put a 4 instead; it jumps to slide 4. Really useful.)
Set destinationSlide to value 7Jump to slide %%destinationSlide%%
2) Go to the slide just before this one. From slide 7, I need to go to 6, to 8, or back to the slide I came from. SOLVED.
From slide 2, you jump to slide 7, from there:^ BACK (goes Back to slide you came from: slide 2)< PREV (goes to slide Previous to 7: slide 6)> NEXT (goes to slide Next after 7: slide 8)
Why has Storyline not been able to "solve" this problem in almost a decade, when all it takes (instead of repeatedly telling people that "previous" works like "back") is to simply create a "back" that works like "back" and let "previous" and "next" be the matched pair that they are in the rest of the digital world?
Sure, ALL existing projects will have to be modified. SO, just create a (FREE) utility that goes through each project and replaces any existing "Jump to Previous" actions into "Jump Back" actions.
OR, set a boolean preference, that can be toggled to the "old, problematic, frustrating way" or to the "new, logical, useful way"
See? It CAN be fixed. PLEASE???
Thanks for listening.
7 Replies
Hello George!
It's helpful to see exactly what would be beneficial in Storyline 360 and understand how it might improve your workflow. I appreciate you listing these details!
To make sure I pass this information correctly to our team, I want to understand what you're requesting fully.
It sounds like you'd like to include navigation settings in variables. This is currently achieved by adding two triggers; one to set the variable and one to determine where the slide navigates to when the variable is set.
I'm happy to share this with our team once I make sure this is exactly what you're requesting. Again, thank you for sharing this with us!
Thanks for the reply Lauren,
What I would really like to see is, 3 (instead of 2) navigation buttons:
BACK (takes you to the slide you just came from, wherever it sits)
PREV (takes you to slide that sits just before this one)
NEXT (takes you to slide that sits just after this one).
(Having been a programmer for many years, variables and triggers are just fine for me. But I meet lots of others that shy away from them. The current built-in functionality allows going to the "Next" slide without any effort, as most of this is automatically done for the developer).
As it's been working for 8 years, "Next" takes you to the next slide, but "Prev" takes you back to where you came from (which may be before or after this slide). So, there's an easy way to go next, and an easy way to jump back. But there is no easy way to go to the slide that is previous (in sequence) to the current slide: there is no actual "previous."
SO, my first request was:
Keep NEXT as it is now. (If I'm on 7, go to 8.)
Add BACK to go back --which PREV now does. (If I got to 7, by a link on 2, go back to 2.)
Fix PREV to go to the slide previous to this one. (If I'm on 7, go to 6, no matter how I got to 7.)
Lauren,
(And again, thank you for responding!)
I suspect my "First Choice" request may not get very far.
Therefore, I offer another request, to provide a work-around for a functionality that is really useful, but still missing.
Can we please have a built-in variable for Current Slide, but make it read AND write, so that if I want to know where I am, I READ the variable. But if I want to jump to some other slide (ANY other slide), I assign that variable a new number (of the slide I want to go to), and it jumps.
OR, at least allow the trigger "Jump to Slide" to read from a variable so that all l have to do is assign a 12 to variable "chosenSlide" and then my trigger can read Jump To Slide "chosenSlide" and the world is a better place for everybody.
Thanks.
Hello George!
Thank you so much for taking the time to lay this out! I understand what you're looking for now in Storyline 360. I'm going to share these with our team in the form of feature requests. We'll update you if they make it on our feature roadmap. Lastly, here's a look into how we manage feature requests.
This would be handy for reviewing too. I have a project that now has a restricted and reduced menu, and lots of lightboxes. I have no way to get reviewers to the 10 slides they need to sign off on. I could just give them a jump box on the first slide and they type in the slide number they want to go to.
(For me, this would be handy if it was built into the Review 360 platform)
Hi Paul,
Thanks for chiming in and sharing your need for this feature!
I've seen one workflow to create a separate copy for review and leave the course unrestricted through the iterations.
When you get to the final review, you can then restrict again to mimic the actual learning environment for final edits.
Not an ideal situation, but it may help save some time!
Thank you. I did find an easier similar solution in the end for reviewing purposes. Unrestrict the menu and add the specific slides being reviewed to the menu, after the current short menu. Then I'll delete the extra menu items after. That has little impact on my work flow.