The attached video explains it all. I want to show on-screen directions only when necessary, and I also want to have a continue button reveal itself after all buttons have been visited.
The best way for us to help is to have us take a look at your slide and run some tests to figure out what's happening with the triggers. Would you be willing to share a copy of your slide with us through a support case? We'll review your slide in private, and we'll delete it as soon as we're done with our investigation.
Based on what I see in the video, it looks like everything should work. That one trigger that hides the second nav prompt should have no impact on the trigger that shows the Continue button. In other words, I can't say why it isn't working. The best suggestion I can offer is to double check what's on the Compound Interest layer to ensure there's nothing there that interferes with proper functioning.
That said, I can't help but wonder why you feel the need to show "Click here" hints at all. Will the users really not know what to do? And, if that is the case, why not just have one"Click each button" nav prompt appear? For example:
Put the nav prompt on a layer.
Put a trigger on the base that shows that layer when the timeline reaches a certain point (e.g., 10 seconds), with the condition that both buttons are in the Normal state.
Note that, if the nav-prompt layer is showing when the user clicks a button, it will disappear when the associated layer appears (assuming the Slide Layer Properties are set to hide other layers).
Judy has some good ideas, as always. However I would add one caution to this:
Put a trigger on the base that shows that layer when the timeline reaches a certain point (e.g., 10 seconds), with the condition that both buttons are in the Normal state.
Be aware that all the built-in states, like most of us, consider themselves to be normal, and will report themselves as Normal. This includes Visited and Selected. So you should write your conditions "if state is not visited, or is not Selected".
Personally, I don't recall ever using "state=Normal" in a trigger. I typically use the "state=Visited" or "state=Selected" options when I'm checking states. So I'm glad to learn something new.
4 Replies
Hi Robbie,
Thank you so much for the video!
The best way for us to help is to have us take a look at your slide and run some tests to figure out what's happening with the triggers. Would you be willing to share a copy of your slide with us through a support case? We'll review your slide in private, and we'll delete it as soon as we're done with our investigation.
Looking forward to hearing from you!
Hi, Robbie,
Based on what I see in the video, it looks like everything should work. That one trigger that hides the second nav prompt should have no impact on the trigger that shows the Continue button. In other words, I can't say why it isn't working. The best suggestion I can offer is to double check what's on the Compound Interest layer to ensure there's nothing there that interferes with proper functioning.
That said, I can't help but wonder why you feel the need to show "Click here" hints at all. Will the users really not know what to do? And, if that is the case, why not just have one "Click each button" nav prompt appear? For example:
Judy has some good ideas, as always. However I would add one caution to this:
Be aware that all the built-in states, like most of us, consider themselves to be normal, and will report themselves as Normal. This includes Visited and Selected. So you should write your conditions "if state is not visited, or is not Selected".
Thanks for that clarification, Walt.
Personally, I don't recall ever using "state=Normal" in a trigger. I typically use the "state=Visited" or "state=Selected" options when I'm checking states. So I'm glad to learn something new.