The layer that should display if I click the Next button - indicating the screen needs to finish before I can go on - will not show as long as the menu is set to "restricted" instead of "free". We need to restrict the side menu to keep the user from advancing that way as well.
I recall my earlier queries on this issue resulted in confirming that the coding in SL2 prevented this from working, and resulted in having to keep my project in SL1. This doesn't ever seemed to have been resolved. I need a solution for SL2. Is there one now?
The key here is that the user clicking the Next button is what needs to make the warning layer appear, so this solution, though appreciated, does not fulfill my need.
There is a potential solution here from Bobbi involving editing an xml file once published. I've used this before and it works great - a really neat work around.
I'm wondering if you actually need the "incomplete" layer. You could have a trigger that sets the next button to disabled when the timeline starts and then another trigger to change the next button to normal when the timeline ends, or when a cue point is reached.
Good point Cary, and that still works with a restricted menu. We wanted a visual indicator for the user, but a disabled button state may serve just as well. But when a user advances a screen, and then clicks the Back button, the Next button is disabled again. I'll need a variable to keep it active once the timeline has ended once.
You could use a object off stage that is timed to appear at the end of the slide and set the trigger for the next button to change states when the state of the object changes states to normal. Then set the slide property to resume saved state.
As far as I can see setting the slide as resumed state results in the slide being at the end of the timeline when revisited. The seekbar is completed and the screen does not replay from the beginning.
Since the next button won't work until the timeline has reached the end, no triggers that you associate with it will work either based on the restricted navigation.
As far as resuming the slide - if you set it to "reset to initial state" on a revisit the user will have to wait again for the timeline to finish before the next button is active again, so you'll want to take that into consideration when setting up your project file.
Cary, a thousand thanks for helping me out - this does indeed work. I duplicated your file and added a few more screens, each with it's unique variable to make the page function like the one you coded. This is really helpful, and I am grateful. I was very close to this solution, but your fresh eyes made it happen!
12 Replies
Hi Richard,
You could set this up so that this layer shows if the user clicks outside "x" if the variable = false.
Please take a look at the attached example.
The key here is that the user clicking the Next button is what needs to make the warning layer appear, so this solution, though appreciated, does not fulfill my need.
There is a potential solution here from Bobbi involving editing an xml file once published. I've used this before and it works great - a really neat work around.
https://community.articulate.com/discussions/articulate-storyline/sl2-restricted-menu-navigation-and-next-button-solution-workaround
Thanks Steve G! I had discussions with the senior support engineer last year and the only solutions offered were to:
1. Rebuild the course navigation using custom Next buttons.
2. Disable Restricted Navigation.
3. Avoid upgrading this course to Storyline 2.
I'll give this solution you linked me to a shot. Thanks!
I'm wondering if you actually need the "incomplete" layer. You could have a trigger that sets the next button to disabled when the timeline starts and then another trigger to change the next button to normal when the timeline ends, or when a cue point is reached.
Good point Cary, and that still works with a restricted menu. We wanted a visual indicator for the user, but a disabled button state may serve just as well. But when a user advances a screen, and then clicks the Back button, the Next button is disabled again. I'll need a variable to keep it active once the timeline has ended once.
You could use a object off stage that is timed to appear at the end of the slide and set the trigger for the next button to change states when the state of the object changes states to normal. Then set the slide property to resume saved state.
As far as I can see setting the slide as resumed state results in the slide being at the end of the timeline when revisited. The seekbar is completed and the screen does not replay from the beginning.
Hi Richard,
Since the next button won't work until the timeline has reached the end, no triggers that you associate with it will work either based on the restricted navigation.
As far as resuming the slide - if you set it to "reset to initial state" on a revisit the user will have to wait again for the timeline to finish before the next button is active again, so you'll want to take that into consideration when setting up your project file.
Hi Richard,
Take a look at this. I think I have got a way for it to work for you.
Cary, a thousand thanks for helping me out - this does indeed work. I duplicated your file and added a few more screens, each with it's unique variable to make the page function like the one you coded. This is really helpful, and I am grateful. I was very close to this solution, but your fresh eyes made it happen!
No problem Richard.
This discussion is closed. You can start a new discussion or contact Articulate Support.