Forum Discussion

AileenLynch's avatar
AileenLynch
Community Member
14 years ago

Previous button

Good Afternoon, This may be a silly question, but it seems as though when I publish at Storyline project the Previous button returns you to the last slide you viewed as opposed to the actual pre...
storyline 360
MikeBethany's avatar
MikeBethany
Community Member
13 years ago

Steve Shoemaker said:

Mike,

I was able to open the Dropbox file and it worked pretty much as I expected with the Previous button returning me to the slide I had viewed before the one I was on.  When I clicked the Previous button again it took me to the slide I had viewed before that (as it should).  I unzipped the file you included to hopefully see the .story file but I didn't see that file, just a bunch of .html, .js and .swf files.  I then created my own test file, similar to yours.  I included a button that jumps to a slide not in the correct numerical order (slide 3.2) and then previewed it.  It works exactly the way I expected it to.  I wrote down the slides in the order I viewed them and then used the Previous button.  Each click of the Previous button took me backward through the order in which I had viewed the slides.

I'm not saying there's not a problem, just that I haven't been able to duplicate it. 

Weird, I just learned that while you do have to have the "next" trigger for the next button the "previous" trigger magically does not have to be there. This is another design inconsistency.

Sorry, I should have been more specific on how to replicate the error:

Go to https://dl.dropboxusercontent.com/u/33392673/BadDesign/story.html

Press "Next" twice, you will be on S1 L3 (Scene 1 sLide 3).

Press "Previous" once, you will be on S1 L2.

Press "Previous" again, you will be on S1 L1.

(This is all expected behavior)

Press the "Next" button three times, you will be on S2 L1 (Scene 2 sLide 1 - a new scene).

Press "Previous" once, you will be on S1 L3. (expected)

Press "Previous" again, you should be on S1 L2 but are in fact on S2 L1 (unexpected).

Here's the storyline file:

https://dl.dropbox.com/u/33392673/PreviousButtonBadDesign.story

--- mega edit conclusion ---

OK, part of it was me putting in triggers that I don't need but it still doesn't address my issue where I have my own navigation buttons. If you use the built in next/previous buttons and don't add a trigger to the previous button they will work correctly.

However, if you have your own menu system and you try to replicate the Next/Previous button functionality using the next/previous triggers it will not work consistently.