Forum Discussion
Button's Hover state doesn't work after mousing over a Disabled button
I created an interaction with 8 clickable, transparent buttons on top of a spreadsheet graphic; each button sits on top of a column in the spreadsheet (shown on the base layer). I present a series of 6 question layers (one at a time). For each question, incorrect clicks change the selected button(s) to their Incorrect state (add a Red X graphic). Clicking the correct button for Q.1 (1) disables that button for the rest of the exercise (Disabled state adds a Green check graphic), (2) resets all other buttons to Normal, and (3) presents the next Question. (I used a variable to track which question is current and therefore which button is correct for each question.)
Each transparent button also includes a Hover state (an arrow pointing to the column), which works fine EXCEPT when you mouse over a Disabled button immediately before mousing over the button. The only way to see a button's Hover state is to deliberately mouse over anything other than a disabled button first. But there are 8 adjacent columns/buttons, and learners will want to move the pointer side to side, which means they won't see the Hover states of the remaining buttons and will miss the next correct answer.
I tried changing the Hover state to simply add an outline instead of showing an arrow shape, but that didn't fix the problem.
Has anyone else run into this? Any ideas on how to fix it?
38 Replies
Has this bug been fixed in any recent updates?
Hi Douglas,
We're still seeing an issue in Storyline 360 and Storyline 3 where the "Hover" state won't appear if you first hover over a disabled object.
I'm sorry this is affecting your project! If we get an update on this, we'll share the news with everyone here in this discussion.
I am running into this issue as well. Are there any updates on when this bug will be fixed?
Hi Monique. No updates yet, but I've updated the impact based on customer reporting. Thank you for adding your voice!
Is there any news on when this bug will be fixed?
Hello Jarryd!
Unfortunately, we don't have a timeline. Our team is looking into the nature of the bug, so I hope we can report back with an update soon!
Thanks for your patience. We'll update everyone in this discussion when we hear of more information!
Hi Lauren
Ive read the threads and work arounds etc. I will be trying them. Don't mean to sound like a broken record, but I'm just wondering why after 3 versions that a feature so simple as a hover state would not work in this version? During the testing stage, didn't the development team see that it wasn't working on their end as well?...or did it work? I'm just saying this because so many people are identifying this problem therefore would it also not have shown up as a problem during the testing phase?
I've run into two or three bugs in the latest version that were not issues in the previous versions :(.
Hey!!...I created my hover using "STATES" and it works perfectly. No wait, no lag...on the mark when you hover over.
Cheers everyoneAs a follow-on to what Yvan said -- my workaround is to insert a hotspot behind the buttons -- it only needs to be one as long as all the buttons are encompassed by it and you can't get to them except by rolling over this hotspot along the way. Put a trigger on the hotspot telling it to do something innocuous (i.e., change a dummy variable) when user hovers. The buttons need to have enough of a gap between them for the rollover of the intervening hotspot to have time to register.... voila. Rollovers work on the active buttons. Unless the user moves his mouse REALLY fast.
Any updates on this bug?
Good morning, Tim!
Thanks for checking in. This bug is still open for investigation, but I'll let the right team know you reached out and keep you posted on any new developments!
