Hi. I am using Storyline 360. I have an interactive slide, where I've disabled the Next button until all buttons are Visited. Then once all objects are Visited, the Next button is turned to Normal.
However, the Next button turns to Normal as soon as the seeking reaches the end of the timeline, regardless of the buttons being Visited.
I found a temporary solution of changing the Navigation Restrictions to Free, instead of Restricted. But eventually, I will need to change back to Restricted after testing is complete.
Lisa, do you have a trigger in there that is enabling the Next button at the end of the timeline? I know that seems obvious, so don't yell at me, it's just that with some projects with lots of triggers, the built-in triggers can get lost in there. Are you able to post an example of your project file?
Hi Lisa. I'm curious. Are you using the course player/built-in Next button or a custom Next button you've created? As Michael mentioned, I think it would be super-helpful to have either the .story file you're working with or a Peek video of the behavior you're seeing during testing.
Thanks for the reply! I'm using the built in Next button. I've Disabled it on the base layer and then set it to Normal on the slide layers once all layers are "Visited". The attached has the Menu settings set to Navigation = Free. When I change Navigation to Restricted, the Next button becomes active as soon as the timeline reaches the end.
Thanks Michael. I have a trigger that Disables the Next button on the base layer, and then additional triggers on each layer that sets Next to Normal, once all layers are selected.
Hi Lisa! Thanks for sharing your file with us. I took a quick look and found that changing from Free to Restricted didn't have any effect on the behavior of the Next button. Your slide trigger to disable that button until all the items are viewed, seems to be working for me.
Here's a quick Peek video to show you how things look on my end! If I've misunderstood the problem, please let me know.
Trina - Thanks so much! Your video confirmed what I was doing and I'm glad to hear that you it works OK for you. Another person replied to me and it worked fine for him as well.
For whatever reason, I still have this hiccup in Preview mode. But when I published it to html5 it worked just fine. So I'm going to move forward. Thanks again for you help!
6 Replies
Lisa, do you have a trigger in there that is enabling the Next button at the end of the timeline? I know that seems obvious, so don't yell at me, it's just that with some projects with lots of triggers, the built-in triggers can get lost in there. Are you able to post an example of your project file?
Hi Lisa. I'm curious. Are you using the course player/built-in Next button or a custom Next button you've created? As Michael mentioned, I think it would be super-helpful to have either the .story file you're working with or a Peek video of the behavior you're seeing during testing.
Thanks for the reply! I'm using the built in Next button. I've Disabled it on the base layer and then set it to Normal on the slide layers once all layers are "Visited". The attached has the Menu settings set to Navigation = Free. When I change Navigation to Restricted, the Next button becomes active as soon as the timeline reaches the end.
Thanks Michael. I have a trigger that Disables the Next button on the base layer, and then additional triggers on each layer that sets Next to Normal, once all layers are selected.
Hi Lisa! Thanks for sharing your file with us. I took a quick look and found that changing from Free to Restricted didn't have any effect on the behavior of the Next button. Your slide trigger to disable that button until all the items are viewed, seems to be working for me.
Here's a quick Peek video to show you how things look on my end! If I've misunderstood the problem, please let me know.
Trina - Thanks so much! Your video confirmed what I was doing and I'm glad to hear that you it works OK for you. Another person replied to me and it worked fine for him as well.
For whatever reason, I still have this hiccup in Preview mode. But when I published it to html5 it worked just fine. So I'm going to move forward. Thanks again for you help!
This discussion is closed. You can start a new discussion or contact Articulate Support.