23 Replies
Brian Allen

Hi Joanna,

You can use built-in image states which include a "hover" state. With these built-in states the hover state works automatically, no triggers required, and will return to the "normal" state when the mouse leaves.

Here's a little more info on image states - https://community.articulate.com/series/4/articles/adding-and-editing-states-in-articulate-storyline-2

Joanna Lau

Hi there,

Thank you! I managed to figure out the hover state. I am having a different issue now in that the hover state still shows the text from the normal state, so they overlap. I've attached images to help demonstrate the issue. What am I doing wrong?

Thank you so much,
Joanna.

Walt Hamilton

Basically, the built-in hover state (like some of the other built-in states) is an overlay of the previous state. That means it does not replace what was there, it merely places the hover state on top of it. If you want something to disappear when you hover, you have to create your own state and triggers.

Brian Allen
Walt Hamilton

Basically, the built-in hover state (like some of the other built-in states) is an overlay of the previous state. That means it does not replace what was there, it merely places the hover state on top of it. If you want something to disappear when you hover, you have to create your own state and triggers.

This has never been my experience, but possibly things have changed recently? I'm normally able to use the built-in hover state very reliably, and have never had this type of overlay problem before. I use them a lot actually.... Strange.

Joanna Lau

Hi Christie, 

Sorry, I guess I'm not sure if I understand. So the hover state literally hovers what is in that state over the normal state so that both overlay with each other? That seems a little strange. How do I create a real hover state where my image and text do not overlay with the normal state?

Thanks,

Joanna

Brian Allen
Christie Pollick

Hi, Joanna -- I see that Walt has stopped in with an option to assist! Please let us know if that will work for your needs. :)

Christie, are you saying that this is the way the built-in hover state is supposed to work? The way Walt is describing it here? Seems broken to me...

Christie Pollick

Hi, Joanna and Brian -- My apologies for the confusion, and I think this might benefit from some additional exploration. I would like to set you up in a case to work with our Support Engineers, Joanna, but I am not able to locate contact information for you in our system, so if you could please use this form to submit a case, I will be on the lookout to follow along. 

Walt Hamilton

Brian,

You are thinking of natural objects, like the blue box in the attached video, which has built-in text. It works like you think it should. The helmet in your story is a complex object (picture and text box) and state changes are applied to only one of them, in this case the helmet. In the attached story, I attached the hover state to the second text box, and it works the way you think it should. Then I grouped the helmet with the text box so that the hover effect kicks in when the helmet is hovered over. NOTE: Now the text changes on hover, but the helmet won't.

Brian Allen

Walt, thanks for the reply.... I've somewhat moved away from hover interactions because of incompatibility with touch devices but it seems like I've still used them recently enough I'd have noticed if they weren't working anymore.

And I totally get what you're saying as far as "natural objects", etc., and appreciate the examples (thank you!), but I definitely remember being able to use objects like my football helmet example before along with the built-in hover state, unless I'm losing my mind which is completely possible.

In any case, the concept of how a hover state should be expected to work is something that has been well established (since the old Flash days for some of us) and if Storyline is simply overlaying the hover state over top of the normal state it still seems broken to me (hopefully). At the very least I'll say that it is not working as I would expect a hover state to work.

Leslie McKerchie

I just wanted to pop in and share an update. I took a look at the case filed by Joanna (00875389) and it does look like the issue reported here has been shared with our QA Team for review and clarification. The workaround being to handle the image and text as different objects and states in the meantime. The overlap seems to only happen on hover and that does not seem consistent. Thanks everyone for sharing.

Brian Allen
Leslie McKerchie

Of course the objects could be triggered together to make it a bit more seamless as well.

True here, as they should trigger together for sure.  More triggers, definitely makes it much more clunky to implement.

I'm hoping that your QA team finds this to be a bug. The expected behavior for me would be for the built-in hover state to handle this without having to use workarounds.

I'm almost positive that this hasn't always worked this way... I'm tempted to install SL1 on my personal machine and see if I can replicate it, lol.

Thanks for putting this example together Leslie and thank you for getting it in front of the QA team, much appreciated.