Forum Discussion
Button State getting stuck when returning to slide
I've got a course menu set up with 4 buttons that have Normal, Hover, Visited, and Down states set up. When the slide loads, the buttons appear in Normal state. When I mouse over any of them, they display the Hover state. When I click on any of them, they change to the Down state. This is all working perfectly. Once I've clicked a button and visited the associated slide though, the button seems to get stuck in the Hover state when I return to the menu slide until I hover over the button again and then mouse away. It's only at that point that the button will display a Visited state. I've attached an example to this discussion.
Kyle,
Built-in states can sometimes create a challenge. Try creating a custom state for the Visited state and adding a trigger. I fixed your .story using this approach.
https://community.articulate.com/discussions/articulate-storyline/hover-state-not-going-away
Richard
It looks like the objects are grouped. If you ungroup them, the states on the buttons work as intended. As a general rule, if I have a trigger on an object, I try not to group them.
Also, you could copy and paste the button text boxes and add those inside the normal state which would mean you don't need to use groups.
Thank you for this. Interestingly, the Integrity template included the text boxes separately and had them grouped so I just left them that way. This fix worked though. Thank you!
I have the same problem Kyle noted in his initial post. Then I followed the suggestions in the comments. I ensured nothing is grouped. Then I tried creating the custom button, but the custom button acted the same way as the hover button. I also read through the responses to this problem from 2 years ago. Does anyone know if Articulate is working on this glitch? How do we get it on the list to be looked at? Thanks!
Hi Susan, and welcome to E-Learning Heroes. 😊
It looks like Kyle was able to correct the issue above. We'd be happy to work with you.
I'd like you to share your project file privately with our support engineers to investigate what's happening with your permission. It will be deleted when troubleshooting is complete.
Leslie,
Thank you so much for reaching out! I look forward to learning from you.
I’ve attached the .story file. It includes a screen recording showing what’s happening to help you understand what I’m seeing.
Thanks for the help!
Susan Gentile | CAMMO Organizational Development
Office: 719.622.4903 Cell: 719.238.5456
Hi Susan,
I'm not seeing your .story file attached here, but it looks like you've replied via email. This does not allow attachments to populate in the forums but does include your email signature. If needed, you can remove that by clicking 'Edit' beneath your response. Here's a quick Peek video if you need help.
Please click 'View' vs. 'Reply' or click here to return to the forums from your email and use the Add Attachment functionality in your reply.
Thanks, Leslie! I realized I had text boxes with triggers rather than buttons with triggers. Changing from text boxes to actual buttons made the difference. Thank you for the assistance!
I'm so glad that you were able to sort things out, Susan. I appreciate the update!
