Forum Discussion
State of next button is not changing
Hi everyone,
I hope you can help me with this...
I have created a slide with 4 pictures. By clicking on a picture the state of the picture goes to visited and this works fine.
I want the 'next button' (initial state = hidden) to appear when all 4 pictures (layers) are visited.
I created a variable on each layer that adds 1 when the learner visits a layer.
I added a trigger on the base slide that says change state of 'next button' to normal when the variable is equal or more then 4.
The next button does not appear...
What is it that I am not seeing?
Please help!
Many thanks
Nathalie
You don't need triggers to change an object to Visited. That happens automatically. (See https://community.articulate.com/discussions/discuss/primer-take-advantage-of-built-in-states/777134 )
For the set up on this slide, you also don't need to use a variable. Just change the custom next button to Normal when the picture buttons are all Visited.
Strangely, that basic trigger wasn't working for me. I think the custom next button was somehow corrupted. I deleted the custom next button, and created a new one. Now the trigger works.
6 Replies
Hi, You probably copied and pasted the previous button, deleted the next button, and redid it, from an imported image.
I do not know what you mean? It is a button that was created by me, so I did not copy it?
You don't need triggers to change an object to Visited. That happens automatically. (See https://community.articulate.com/discussions/discuss/primer-take-advantage-of-built-in-states/777134 )
For the set up on this slide, you also don't need to use a variable. Just change the custom next button to Normal when the picture buttons are all Visited.
Strangely, that basic trigger wasn't working for me. I think the custom next button was somehow corrupted. I deleted the custom next button, and created a new one. Now the trigger works.
Thanks Judy!
The next button is hidden on all your layers...switch that "ON" and it should work as intended.
Excellent sleuthing!
I think I've seen more cases of issues from corruption than from hiding objects on the layer (especially since that isn't the default). This is a good reminder to check for settings that impact visibility.
