I have a series of buttons that all change states when hovered (name of button appears) , selected (name and description of the button appear) and deselected (returns to normal).
The problem I am having is if a button is selected (name and description of the button appear) and then the user hovers over another button (name of button appears), information from both buttons appear. Any suggestions how to force the user to "deselect" the button before information from other buttons show?
I'm not sure I understand. Looking at the .story file may help give a better visual. What I could do is change the state by adding a background to the descriptions (in this case a gray square behind the text). What I would really like is to learn how to solve this issue using conditions and variables. But that may not be possible.
Okay, I retract my silliness. I am unable to turn these buttons into a button set. Would someone please look it over and see what it is I am missing? Note: the Hover state in one button may not be the same as another. Thank you.
7 Replies
I dont have time to open and investigate the .Story right now, but,I assume these are states of the button.
for example: buttons A - D each have a state for normal, hover, select.
You could set it up so:
when user hovers over Button A , change state of button A to Hover.
When user Hovers over Button A, change state of button B to normal.
When user Hovers over Button A, change state of button C to normal.
When user Hovers over Button A, change state of button D to normal.
You would need to repeat this process for each button.
Its a long and annoying way to solve the issue, but its all i got right now. Ill see if i can come up with a better solution tho.
I'm not sure I understand. Looking at the .story file may help give a better visual. What I could do is change the state by adding a background to the descriptions (in this case a gray square behind the text). What I would really like is to learn how to solve this issue using conditions and variables. But that may not be possible.
You could also try button sets. They work nicely https://community.articulate.com/series/4/articles/adding-button-sets-in-articulate-storyline-2
Yes, but that would be too easy, wouldn't it? Where is the sport in that?! I feel silly. Thank you Richard Hill.
Okay, I retract my silliness. I am unable to turn these buttons into a button set. Would someone please look it over and see what it is I am missing? Note: the Hover state in one button may not be the same as another. Thank you.
I didn't know that using the hover state would complicate it so much. So this is more of a design fix. But it works.
A design fix is what I will focus on. Rich, thank you for all of your help.
This discussion is closed. You can start a new discussion or contact Articulate Support.