Sticky Hover-Over State

In my project, my strategy uses "Hidden" as the default state, and "hover over" triggers over shown elements to reveal information about those elements ("Restore on Mouse Leave"  returns the information to the default "Hidden" state).  It works beautifully EXCEPT that ONE of my interactions (MyProfile element) fails to consistently return to the default "Hidden" state; it's like the hover state is "sticky". When it doesn't return to hidden state, layers of images and text overlap. The frustrating part: sometimes it does what it's supposed to do, & sometimes it doesn't! 

I've tried copying one of the other elements where I DON'T have this problem and reworking it in place of the problem element, but this issue persists.  I suspect it has something to do with the fact that half of the elements are on one layer, and the other half on another layer (a convention I use just to help manage the complexity of the timeline), because it seems to fail when the mouse transitions between elements on the two layers (for example, from "Main" to "My Profile" and vice versa).

Has anyone out there run into similar problem and have a recommended fix, OR have a theory about the problem root cause that could lead me in another direction?

9 Replies
Brad Pepin

After posting this, a noticed a discussion thread recommended that I had not seen before.  In it, Ashley T recommends programming another trigger to change the "sticky" state back to normal (hidden, in my case) when the mouse hovers over another area - such as a transparent shape around all the arrows or a hotspot.  It's not perfect, but that safety net of "resetting" the sticky hover when the mouse moves to the adjacent elements is helping it better.

I also increased the separation between the elements in hopes that might make a difference or remove any weird interference experienced by the state of near-overlap of the elements. 

Steve Semler

I'm having a similar problem, maybe. (Maybe not?) The object on the base layer has a "change state of object when mouse hovered over" with "restore on mouse leave" checked. This changes the color of the wedges in the wheel. When a wedge is clicked, it shows a layer with more information. Sometimes, however, the base layer wedge will not return to its Normal state on mouse leave. At that point, nothing will change it back to Normal state.

I think this is happening because the mouse cursor ends up on the layer that is shown before it "leaves" the base layer wedge object, but I have set up the shown layer objects to not interfere or overlap with the base layer wedge that is clicked. (I think.)

Any suggestions?

(posting to this thread because the "sticky" hover-over state seems most similar.

Katie Gokhshteyn

Thanks for sharing your project, Steve! Here's a quick Peek of what I saw–quite strange!

I don't see anything in your setup that would cause the wedge lag, so I'd like to get more eyes on this. I've shared your file to our Support Team for a closer look. They'll reach out to you with their findings via email soon. Keep an eye out for that email, and I'll follow along as I'm really curious to know what's causing this!

Steve Semler

Thanks, Katie.

The Peek video looked like it was working as intended. Was that in a SL360
preview, or published? I have not tried... wait, no I did. I have the same
behavior in the preview and in the Articulate Review published version I
shared with the team. Never mind. :)

But I have been viewing/working on it only on my Win7 machine with SL360
and the Chrome browser. I have not tested other machines or browsers, at
this point.

Please do let me know if they find anything. I will watch the support case
messages.

Ashley Terwilliger

Hi Steve,

That Peek video from Katie appears to be in the web published output. 

I see that Renz is also testing, so he'll be in touch as soon as he has information to share. 

Also, just a note -  Replying via email will include your signature. You can edit out your contact information from your post if you'd like!  

 

Steve Semler

FIXED. For future visitors, here is our best guess about the root cause and an effective solution:

Root Cause: The wedges are slightly larger than the adjacent objects, and so overlap those adjacent objects. If the user clicks on the adjacent wedge, the mouse cursor sometimes has not registered as having left the initial wedge object, so the return to normal state quality doesn't activate.

Solution, Part 1: When creating and laying out the objects, try to make sure that they won't overlap in any state when using this kind of interaction. (Acknowledged: Sometimes that's really tricky.)

Solution, Part 2: Add a slide trigger that changes the state of the object back to normal when the user clicks outside of the object. This effectively "resets" the object to normal when it is not the active subject of the learner's attention.

Example Syntax:

  • Action: Change state of
  • On Object: Slice2
  • To state: Normal
  • When: User clicks outside
  • Object: Slice2

(Special thanks to Renz S. on the Articulate Support Team for this analysis and fix!)