Something wrong with trigger on this slide
Dec 13, 2021
By
Amit Goel
Hello,
I think this is a fairly simple one, but I can't figure it out.
In the attached slide, I would like the NEXT button to show after the user has clicked all 3 blue boxes. Very simple, I thought. Just a trigger that says to change the state of NEXT from hidden to Normal after the state on all 3 boxes is visited.
But for some reason, that trigger was hit or miss. So I added a variable that changes to TRUE when all boxes are visited. And when that variable changes, the NEXT button becomes visible.
That seems to work, but there are still one or two people who are not seeing the NEXT button after all boxes are clicked.
I feel like I'm missing something very simple here. Any help would be appreciated.
Thanks
Amit
5 Replies
Amit,
Try adding the conditions to the trigger as shown below and see if it works.
Richard
Hi, Amit.
Thank you for sharing your .story file!
Your project worked as expected 99% of the times I previewed. However, on a few tries, depending on how long I spent on the last layer, the Next button would show up very small on the screen:
I believe this is connected to the Grow entrance animation, so I went ahead and opened a support case so we can investigate this issue. We'll reach out via e-mail!
In the meantime, I suggest removing the animation as a workaround.
Thank you both for the help.
Richard, I will add that additional item to the trigger (Condition).
Maria, thank you for the suggestion. I will remove the animation and then wait to hear from you via email.
Maria,
I also noticed the odd behavior in the preview. I've seen that several times on other Storyline projects I've worked on in the past few weeks.
Amit, that last part to the trigger may not be necessary if the problem is with the corrupted states but it could create a different result if you were toggling the variable from T/F in another type of interaction... hence the reason I added it.
Richard
Good point, Richard, thank you!
Maria, thank you for referring this issue for extra help. Someone did reach out to me with a solution. He said the initial NEXT button I created was the culprit. He removed it, rebuilt it, and it works! I also removed the grow animation and kept Richard's variable idea just to be safe.
Thanks, everyone!