Nicely styled buttons. Can I ask, is there a technical reason why they are built with so many elements, boolean variables and a hotspot? Could the button be simply built with a single disc and an additional chevron inside the state while making use of the built in hover function?
https://360.articulate.com/review/content/b7382f67-2c16-4c83-b7fd-294c03c9cb70/review
Thanks for the comment Dom and sorry for the late reply as didn't see it.
I've left all the elements to show how it was built and make it easy to modify.
Of course you could add all the elements to the state and have one simple object :)
In my demo you can see that one button has active and disabled states both activated on hover. That's why I've used variables so it's easy to switch on/off the states. In this setup you can have multiple hover states. If you need only one then it's better to use default hover.
Hope that's clear :)
@Dom Sweeten, this is just a guess, but since the buttons will change to different colors on mouse-over to indicate "disabled" or "active," the extra elements may be to ensure that mechanic works properly. Sometimes triggers based on things like a visited state don't work reliably, so I resort to variables instead.
9 Comments