Forum Discussion
Prev and Next Buttons Are Moving to Random Slides
Hi!
I am having a problem with slide navigation. I have published an HTML module that runs off a website. This module was originally created in an older version of Articulate SL and has been updated to the current version. It worked perfectly before.
There are two scenes...the "training" scene that contains a linear intro and branches for each quiz, and a "complete the course" scene which is a linear path for printing a certificate and sending it off to a set address.
- If you use the player buttons to navigate linearly from the very beginning in the Training scene, the PREV and NEXT slide buttons work correctly.
- If you choose a page from the player menu (lists only pages up to the Quiz Menu), the PREV and NEXT slide buttons usually work correctly.
Completing the module scene
This is where things get really strange. The PREV and NEXT controls are inconsistent. Sometimes they work and sometimes they hop all over that section. When I navigate linearly and get to the final slide, I am stuck there because the PREV button no longer works. I have to use the player menu to go back to the Quiz menu to access the link to the Module Results at the start of the section. Then when I use NEXT and PREV to navigate, it is a roll of the dice. Sometimes it's the previous screen, sometimes it's the final screen or if the user generated a certificate, it's that. Can the View Certificate slide code is throwing off the navigation code somehow? Does it need to see the slide as "complete" or "initial state" for the button code? If so, is that a setting in the player? I'm looking at restricted and free settings in the articles, but not sure how to apply it here.
Thanks!
Marcia
Hi Marcia, I haven't looked into your file, but this sounds like the curse of the PREV button and what the "previous slide" trigger actually does.
The "previous slide" trigger is using history, and determines the slide to go back to based on where you have come from, and not the previous slide linearly. In your example, it works fine when you progress through the module linearly. This makes sense, as the previous slide in history, would correspond to the previous slide linearly. Where that gets broken is using the Menu.
The only fix for this, and one I use out of muscle memory now, is to specify the slide the PREV button should go back to. Yes, this means setting every PREV trigger to go back to a specific slide (the one before the current slide).
I find this to be a bug bear that pops up a few times. It would be great to be able to configure project to either use "history" or "linear".
Sam, I very much appreciate your help with this!
Seeing the coding on the player triggers I can see exactly what part of the issue is and it makes sense given your logic tips.
Thanks a mil-it's FIXED!
Marcia
