Hi folks, new-ish to Storyline. I have three buttons. All should work independent of each other, but right now the hover states (and maybe others) appear to be connected. If I hover over the first button, others are active as if they are being hovered over. How do I fix this?
Replying to my own post, it seems like my button hover states get corrupted or confused pretty easily. My steps:
I deleted the "broken" buttons and copied/pasted new button w/o any associated triggers.
Tested the hover states and they appeared to work fine.
Added some triggers to the buttons, tested, now the hover states are broken again; if I hover over my first button then ALL act like they're in the hover state.
This is odd. Buttons shouldn't inherit their hover state in this way, OR there should be an easy means of editing it (is there? I can't find it.)
What triggers have you added to the buttons? If you're using the standard buttons the hover state doesn't need a trigger and buttons will behave as described here. Have you grouped the buttons perhaps so that they're all operating as one element? If you'd like us to take a look you can share a copy of the .story file here with us.
Hi Ashley, thanks for following up. I meant to update the thread, but YES, it was due to GROUPING. My intuition was that the hover states wouldn't have be associated with grouping status, but I can also understand the rationalization for the behavior too. Perhaps an option to retain hover states when grouping?
4 Replies
Replying to my own post, it seems like my button hover states get corrupted or confused pretty easily. My steps:
I deleted the "broken" buttons and copied/pasted new button w/o any associated triggers.
Tested the hover states and they appeared to work fine.
Added some triggers to the buttons, tested, now the hover states are broken again; if I hover over my first button then ALL act like they're in the hover state.
This is odd. Buttons shouldn't inherit their hover state in this way, OR there should be an easy means of editing it (is there? I can't find it.)
Hi Ben,
What triggers have you added to the buttons? If you're using the standard buttons the hover state doesn't need a trigger and buttons will behave as described here. Have you grouped the buttons perhaps so that they're all operating as one element? If you'd like us to take a look you can share a copy of the .story file here with us.
Hi Ashley, thanks for following up. I meant to update the thread, but YES, it was due to GROUPING. My intuition was that the hover states wouldn't have be associated with grouping status, but I can also understand the rationalization for the behavior too. Perhaps an option to retain hover states when grouping?
Sounds like a good idea for a feature request, as otherwise since they're grouped I'd expect them all to behave the same.
This discussion is closed. You can start a new discussion or contact Articulate Support.