Next/previous buttons
Apr 30, 2021
By
John Glasgow
Hi, anyone familiar with the following problem?
I have slides with Next/Previous buttons, which contain multiple slide layers.
By default the same Next/previous buttons are displayed on the slide layers and there does not 'appear' to be any way to suppress them.
Which means that the user can accidentally bypass slide layers if they choose to use the next button on any of the slide layers.
The only way I can see to prevent this is to not display the next/previous button on the base layer at all, which means inserting a trigger and an instruction to inform the user how to proceed. Anyone got a better solution?
4 Replies
In this case, I typically rely on triggers and variables to make the Prev/Next buttons active or inactive. How I do it depends on how my layers are set up (e.g., if they must be visited in order or if they can be visited in any order). Here's my setup if they can be visited in any order:
Each slide layer has a variable associated with it, and when the layer is visited a trigger sets that variable to TRUE.
The base layer has a trigger to disable the Next button at the start of the timeline IF those variables are false.
Each additional layer has a trigger that will make the Prev/Next button active at the start of the timeline if all those layer variables are true. That way, in case they revisit the base layer, it will still do a check that all layers have been visited and allow the person to navigate forward at will.
Hi, John,
It sounds like you don't want a user to be able to click the built-in Next button in the Player until after they have viewed all the layers in a slide. If that is what you're asking about, the solution is to disable the Next button until the layers have been viewed. Here's how to do that:
If you're using a custom Next button, you could control it the same way.
If you're not familiar with conditions and variables, you can find out more in Articulate's User Guide:
Great thanks Kalena, will give that a go.
Best regards
John
Thanks Judy, seems like a lot of effort just to force the next button to behave in the way you want, but at least its a solution.
Thanks
rgs
John