Forum Discussion
Storyline 360: after button disables self on mouse hover, cannot return it to normal
I have a button that has multiple triggers on "mouse hover over," as well as triggers on mouse-click. One of the on mouse hover triggers detects when a variable (temp) is '0'. When this happens, a hidden alert text box is activated and the button is supposed to disable itself (see below), so that the user can't click the button to progress (until they've adjusted temp to higher than 0). Note that I have "restore previous state..." checked, so presumably, when the mouse hovers off the button, it should return to normal. However, this isn't working, as the button gets stuck in disabled. I'm guessing it's because, once disabled, it can't detect the "mouse hover off" action??
I've tried a few workarounds, such as creating a hotspot (as well as a transparent shape) in front of the button to handle the button's mouse hover triggers, while leaving the on mouse click triggers on the button. But both of those objects (hotspot and transparent shape), even though they're invisible, while handling the mouse hover triggers, effectively block the button behind it, preventing it from being clicked.
I'm fairly new to Articulate, so there's probably a quick workaround I'm not aware of yet. But it seems to me that, either (a) the trigger wizard should gray out the "restore previous state..." checkbox if the button state changes to disabled (thus preventing any further interactivity, if that's what's causing this issue), or (b) this could be a bug.
Would appreciate any advice, pointers. Thanks in advance!
3 Replies
I gave up trying to find a way to do this, and ended up using a workaround, whereby clicking the button would trigger an intermediary slide that showed the alerts, based on the values of any variables that didn't meet certain conditions.
I agree with your assessment that the "Restore" option isn't working because no triggers work when an object is disabled.
It would be nice if the "Restore previous state when the user hovers out" option wasn't available if hover trigger is changing the object to Disabled. FYI: You can suggest that here: https://www.articulate.com/product-feature-request/
Personally, I think your workaround is better anyway. Those on a mobile device or using a keyboard (instead of a mouse) can't hover. So, from an accessibility standpoint, no content should be revealed nor important actions triggered via hovering.
That's a good point, re: accessibility and hovering. Thanks. I'd actually prefer if the "restore previous state when the user hovers out" could work in this case, although I realize that would entail programming a "limbo" state of sorts for an object when it self-disables on mouse hover. I guess it's too fringe a use case.
