Hi, I am in the process of creating an e-learning module with lots of screen capture demonstrations. The module has 120 slides! There are 8 scenes and the player's back/ forward buttons are hard wired between scenes but not within them. When I publish it in our LMS and press some back buttons it randomly throws me a few steps back. There must be an easy solution! I appreciate any advice.
Did you set up the "jump to previous/next" triggers after Cheryl's suggestion, as you originally mentioned that the triggers were not hard wired between slides? Scene numbering and slide number could be playing a roll based on how you've set up the triggers, and you may want to begin by reviewing this screenr from David Anderson:
If you're still having some difficulty, could you share the .story file or even a section here with us so that we could take a look?
Something else to consider Dmitri is how the "Prev" button works in Storyline. If you are meaning the "Prev" button when you indicate "the player back" button, this will take you to the screen you looked at immediately before, which may jump a learner to an unintended slide.
E.g.
Imaging you have a linear course of 5 slides: 1-2-3-4-5
You are on slide 5
You use the menu to take you to slide 4
If you click "prev" button you will go to slide 5 as you were there previously
Not slide 3 as you might expect
Personally I find this confusing so I don't use the player buttons in my courses, but to each their own.
"If you are meaning the "Prev" button when you indicate "the player back" button, this will take you to the screen you looked at immediately before, which may jump a learner to an unintended slide."
I'm a creating a project that is very important to use the menu navigation. It's strange how usabiity menu works in SL2...
This explains the problem well. I was scratching my head as to why the pages jump around in a published course. It truly is confusing because students assume previous means back one page.
Glad that Stanton's explanation assisted you here.
Also, the default trigger for the Prev button, which jumps to the last visited slide, is hidden in Articulate Storyline. If you customize the Prev button with an additional trigger—for example, to adjust a variable—it replaces the default trigger. As a result, you'll need to add another trigger to restore the default Jump to previous slide functionality.
Worst: if the last page viewed happens to be a layer (as opposed to a slide) and you press "Back" it won't take to you to it, it'll take you to the last "slide" viewed ... :(
Although this forum discussion is a bit older, the same behavior holds true for the set up of the previous button.
As far as returning to a layer on a particular slide, if you haven't set it to hide that layer and are using the revisiting properties of "resume saved state" you should be able to return to where you left off and see that last layer.
20 Replies
Have you considered adding Player Triggers to each slide to define jump to next and jump to previous slide?
Yes, they are all in place.
It just came up to me that the numbering of scenes might have something to do with this. My ones are not odered as 1,2,3 etc. Any thoughts?
Hi Dmitri,
Did you set up the "jump to previous/next" triggers after Cheryl's suggestion, as you originally mentioned that the triggers were not hard wired between slides? Scene numbering and slide number could be playing a roll based on how you've set up the triggers, and you may want to begin by reviewing this screenr from David Anderson:
If you're still having some difficulty, could you share the .story file or even a section here with us so that we could take a look?
I'm sure you're right. The screenr Ashley referenced shows how to get your scenes to renumber in the order you want.
Something else to consider Dmitri is how the "Prev" button works in Storyline. If you are meaning the "Prev" button when you indicate "the player back" button, this will take you to the screen you looked at immediately before, which may jump a learner to an unintended slide.
E.g.
Stanton
Good explanation Stanton.
Gosh! You guys are sooo helpful. It works now thanks to Stanton for a simple explanation and Ashley for the video link.
Glad we could help here Dmitri!
You are welcome. Glad I could help.
Stanton.
Hello!
So the only way to solve this is putting specific triggers on each slide? (jump to X and jump to Y slide)
Now I feel bad :(
Hi Ek! This thread is a bit dated.
Could you share what issue you are having so that we can try to assist.
Hi, Leslie.
It's the same situation Stanton mentioned:
"If you are meaning the "Prev" button when you indicate "the player back" button, this will take you to the screen you looked at immediately before, which may jump a learner to an unintended slide."
I'm a creating a project that is very important to use the menu navigation. It's strange how usabiity menu works in SL2...
Gotcha, thanks for the explanation. Stanton did explain it great above as well.
If you wish to see this handled differently, you are welcome to share your thoughts in a feature request.
Thanks you Leslie.
I really have some ideas to share :)
Thanks Ek Mon :)
This explains the problem well. I was scratching my head as to why the pages jump around in a published course. It truly is confusing because students assume previous means back one page.
Hi Teresa,
Glad that Stanton's explanation assisted you here.
Also, the default trigger for the Prev button, which jumps to the last visited slide, is hidden in Articulate Storyline. If you customize the Prev button with an additional trigger—for example, to adjust a variable—it replaces the default trigger. As a result, you'll need to add another trigger to restore the default Jump to previous slide functionality.
Worst: if the last page viewed happens to be a layer (as opposed to a slide) and you press "Back" it won't take to you to it, it'll take you to the last "slide" viewed ... :(
Hi Gabriela,
Although this forum discussion is a bit older, the same behavior holds true for the set up of the previous button.
As far as returning to a layer on a particular slide, if you haven't set it to hide that layer and are using the revisiting properties of "resume saved state" you should be able to return to where you left off and see that last layer.
This discussion is closed. You can start a new discussion or contact Articulate Support.