Forum Discussion
Button Hover States are getting stuck
Hi Community! I'm editing a project file that has a few menu slides throughout the course. The buttons are built with the standard Normal, Hover, Selected, and Visited states. When you return to the menu slide, each button is showing as Visited but is stuck in the Hover state. You have to move back over the button to have the Hover state disappear. Any ideas on why this is happening?
Hello, thanks everyone for bringing this to our attention. Our engineering team is currently looking into this and I will circle back with an update when I have something to share.
Hi All!
I'm happy to share that we just released Storyline 360 (Build 3.84.31647.0) which includes the fix for the bug:
- Hover state gets stuck when you quickly move your mouse over objects with hover states
Now all you need to do is update Storyline 360 in your Articulate 360 desktop app to take advantage of the newest bug fixes and features!
If you run into any issues, please don't hesitate to reach out to our team by submitting a support case.
When you click on it, you are also hovering over it. So if your slide is set to saved state on revisit, the hover state is still showing. It will show until it feels a the cursor moving off. You can set the slide Tom restore to initial state, and that won’t happen. Of course, the visited state won’t show either.
One cure is to delete the hover state. Another is to reset the slide on revisit, then when the timeline starts, set all the buttons that have been clicked to visited. You’ll need to create variables (T/F works best) To keep- track of them.
Personally, I prefer not to use hover unless it is the only action. If the button has to be clicked to function, I don’t use hover. I always use variables, for the increased reliability and flexibility they give me.
Hi Walt,
Thanks for the quick reply! I've checked some of our other project files with a similar menu screen set up, and all buttons show only the visited state when you return. The only difference is that there are not Selected button states on this menu. I tried deleting the Selected state of a button in the file with the stuck Hover state issue, but it was the same result - when you return it is showing the Hover and Visited state.
It does seem like this can be fixed without variables as the other project's buttons are remaining in only the visited state when you return to the menu screen.
Any ideas on why there is a difference between these two projects?
Any guidance is greatly appreciated!
Hello Brad,
What Update are you currently running? Also, are there any added borders, etc to your "hover" state?
Hi Ron,
This project is showing v3.72.29699.0. The hover state for this button has the same outline as the normal state. The visited state has a checkmark that appears and an inner shadow effect.
Any guidance is greatly appreciated!
Best,
Brad
Thanks for the info Brad. Also, is anything grouped or added to the states other than the check mark?
Update 72 contained a fix for this behavior. So, if you are still experiencing, I would submit a case, so that the support team can log what circumstances are causing it in your case.
I see earlier in the thread you mentioned the inner shadow on the Visited State. Remove that shadow and you should be golden.
This behaviour seems to have crept back in with version 3.83.31444.0
My buttons sometimes remain on Hover once I've moved the mouse away. Happens to any of my buttons, not just specific designs.
v3.82.31354.0 seems fine.
I can confirm I'm dealing with the same issue since the 3.83.31444.0 update. Installing 3.82.31354.0 also fixes it for me.
Thank you for adding to this thread, it saved me from even more troubleshooting.
I added a screenshot to show what the problem with the Hover states looked like on my end when publishing with 3.83.31444.0.
Hello,
Could I add to the list to confirm that this issue is affecting us too. Our most recent update was December 13th '444.0'. It is as though the curser sticks to a hover state.
Many thanks
Please add me to the list too. I'm also using 444.0.
