hiding previous/next buttons

Jul 18, 2016

I have a slide where I want to disable the next button until all layers have been viewed.  So I set it so when the timeline starts the next button is disabled, and when the state of the buttons to activate the layers is visited, the next button is normal.  The problem is that when the layers are visited, the next button goes back to normal.  I tried to hide it during the layers as I have a button to return to the base layer once the layer is viewed, but the layer button controls override the base layer controls and then the next button doesn't reappear.

Is this something to do with the order of the triggers?

21 Replies
Teresa Hirata

OK.  I was trying to get it to force the learner to go back to the base layer before heading to the next slide, but as soon as you visit the second layer the next button is re-enabled... So they have two choices of buttons.  I kept both layers with "next" buttons to take them back to the base layer so they could access the layers in either order and still get back to see the other.

Is there no work around to send them back to the base layer first?

Teresa Hirata

Now I'm stuck with a similar problem on the Tabs slide... It references multiple slides which all return back, and I need it to go the final slide once all of the others are complete.  But I can't get the next button to re-engage once they are all showing as visited.

I used Walt's solution for the previous problem, but now can't figure out how to get to the finish.... :-(

Walt Hamilton

If you are going to different slides, you need Leslie's solution. My solution is simpler, but it relies on the layers being part of the main slide. Therefore, they can change the state of the NEXT button. Visited states are not as reliable when you visit other slides as they are when you visit layers on the same slide.

Leslie uses variables to mark sections as visited, and variables are pretty much bulletproof; they will always work, while states (like Visited) are much more fragile.

Walt Hamilton

Here's a little something to get you started.

I created variables and triggers for My Profile, New Request, and My Summary. Think of variables as little notes written on the whiteboard to help the kids remember who has done what chore today. For something like "has the user visited this section?", I prefer True/False.

1. There is a trigger on the slide to change NEXT to normal when the timeline starts if all the variables have been completed. (I wrote it only for the 3 I created.)

2. Since the user can't click the NEXT button on the other slides until they complete the activity, it is a good way to know that they have completed it, so clicking the NEXT button on each slide sets the corresponding variable to true. Warning: changing the variable must occur in the list before the jump to the Main Tab slide, because once the jump is started, all other triggers in the list are forgotten.

3.There are custom states on the buttons that I created by copying the visited states. The built-in states have their own agendas and triggers, and that sometimes conflicts with mine, so I create my own states and delete any of the built-in ones that might conflict with them. In this case that's the visited state.

When the Main Tab slide's timeline starts, it checks and changes the state on any button that has been visited, and if they all have been visited, makes NEXT visible. If it doesn't work, sometimes you need to set it to reset to the initial state.

Walt Hamilton

If DocumentDone is changed on another slide, this slide will not be able to notice it changing, and the trigger won't fire.

This trigger needs to be set to When timeline (of the slide) starts.


I don't know if this happens on any other slides, but the jump here occurs before the variable is changed, and once the jump starts, all other triggers below it in the list are forgotten.




This discussion is closed. You can start a new discussion or contact Articulate Support.