Next button not changing states when other objects change to "selected" state
Mar 21, 2023
I have a slide with several layers and need the learner to return to the base layer after visiting each slide layer. On each slide layer they need to perform some simple actions - mainly clicking a few objects (ovals.) I have the Next button set to "change state of button to disabled when the timeline starts on this layer". Then I added a trigger to "change state of the button to normal when the state of all ovals is selected." What seems odd, is that once I set the trigger, it reads "change state of button to normal when the state of all rectangles is selected." Could this be the problem? If so, how do I fix it?
I have checked...all Ovals have a "selected" state, all Ovals have a trigger to change to "selected" state when the user clicks the same Oval, the Oval selected state seems to be working fine - it includes a color change so I can see it has changed. The state changes of the Ovals seems to be working, but they don't trigger the button state change. I have checked the triggers for the button as well - the disable trigger, and change to normal trigger appear to have been written correctly. This seems to simple...but I'm stuck. Thanks in advance!
I've attached a photo of the triggers that I think may be causing the problem.
8 Replies
Photo didn't attach to OG post.
Delete the triggers that change the ovals to Selected state when clicked.
Selected states have a built-in superpower to change to Selected when clicked. Creating a trigger that duplicates that action can frequently cause conflicts with unpredictable, but usually unpleasant results.
If that doesn't work, and it might not, use Visited state instead of Selected. If that doesn't work, you will have to attach your .story file here, so someone can take a look at it.
Deleted indicated triggers, used Visited state instead...still no results. I can't attach my files - protected information. Any other ideas on how to set up a button state change? I've been focused on this problem so long my brain is mush...
Also, any idea about why the trigger reads "rectangles" instead of ovals or even objects? I have a feeling that is the source of the problem but can't figure out how to change it.
Thank you so much for the quick response!
This post was removed by the author
Hi Amy,
You don't have to share the entire project, just the slide/s with the affected shapes. Being able to see the actual affected slides will help us figure out what's happening. You can also share your project file in private by opening a case with our support team here. We'll delete it once we're done testing!
If you are unable to share a copy of the affected slides, try importing your slides over to a new project file to see if this helps. Here's how:
Additionally, are you able to share steps on how you were able to arrive at the issue? I tried replicating the behavior on my end, and it appears that the ovals are being recognized as actual ovals and not rectangles.
Looking forward to hearing from you!
Hi
I found this post following my search for a similar issue.
I have four buttons on a slide with corresponding layers for each one. I have set states for the buttons on the slide to be normal and visited but when the user returns from layer to main slide the button is not displaying as visited.
It works perfectly on other slides/layers but not on this one.
Any ideas?
Thanks.
Dorothy
Hi, Dorothy!
Thanks for reaching out and detailing what you're seeing. Is it possible to share your file with our team? We'd be happy to take a closer look to see what's going on. You can upload it here or share it privately in a support case, and we'll delete it from our systems once troubleshooting is complete.
Hi Kelly
When I was preparing to send the file to you, I had another attempt to resolve the issue. The problem seems to have been with the slide itself - I've just created a new slide with new buttons and copied content and triggers over - and visited states are being displayed correctly.
Thanks.
Dorothy
Hi Dorothy,
That's great to hear you were able to resolve the issue! If you run into any trouble moving forward, please let me know and we'll be happy to help.