Some people put a hotspot under the object. When the mouse leaves, it essentially is moving over the hotspot and can be used as a trigger that is activated when leaving an object.
Of course, it depends on what you're triggering because you mouseover the hotspot to get the original object.
Working with Tom's suggestion you could make a transparent shape that covers the whole slide visible when you hover over an object and then hidden when you hover the shape, if you have an exit animation on the object you could run triggers of the exit animation or run triggers off hovering over the shape.
The other possible thing is to show an object offside when you hover and then trigger anything off the timeline end of that object, if you have it set to restore on mouse out.
I am unable to get this to work. I have a small shape on top of a larger background shape. I'm using a custom hover state to change the appearance of the top object on mouseover. This works.
I have an action that us supposed to change the state of the top object back to normal when the mouse moves away from the top shape and over the bottom shape. This doesn't work. Neither object is transparent, so that's not the issue.
Oddly, if I move the mouse all the way outside of both objects (over the background) and then back onto the bottom shape, it does trigger the desired state change on the top object.
I jumped into your file and came across the same issue. It seems the mouse over trigger doesn't take effect until you're hovering over from outside the bottom box.
For your example, instead of adding the bottom box, why not select the Restore previous state when user hovers out in your top box trigger? I know that doesn't answer the question of how to trigger on mouse leave, but maybe that'll work in your situation!
I think this is a regression bug. I'm pretty sure I've used this technique in the past. And it seemed to work for other people on this thread. I'll submit it to support to get it on the bug list. This is pretty basic functionality and we've spent a lot of time trying to find a workaround.
We can't use restore previous state because we have three states and not two. Depending on the situation, we may need to skip the most recent state and return to the original. We could do this with "if" statements on actions if the mouseover worked on the underneath shape. I'm not aware of any other way to achieve this.
We've experimented with built-in state changes, but found they behave erratically or are designed in ways that don't make sense from a UX perspective. For instance, the rollover state takes precedence over the selected state. So if a user clicks an object to select it, they don't see the selected state until they move the mouse away from the object. There's no visual feedback that they made a selection.
9 Replies
Some people put a hotspot under the object. When the mouse leaves, it essentially is moving over the hotspot and can be used as a trigger that is activated when leaving an object.
Of course, it depends on what you're triggering because you mouseover the hotspot to get the original object.
Working with Tom's suggestion you could make a transparent shape that covers the whole slide visible when you hover over an object and then hidden when you hover the shape, if you have an exit animation on the object you could run triggers of the exit animation or run triggers off hovering over the shape.
The other possible thing is to show an object offside when you hover and then trigger anything off the timeline end of that object, if you have it set to restore on mouse out.
I made a transparent rectangle that appear when I hover the image and disappear when hovering itself and it work great!
Thank you very much! I can finally add motion path on hover!
I am unable to get this to work. I have a small shape on top of a larger background shape. I'm using a custom hover state to change the appearance of the top object on mouseover. This works.
I have an action that us supposed to change the state of the top object back to normal when the mouse moves away from the top shape and over the bottom shape. This doesn't work. Neither object is transparent, so that's not the issue.
Oddly, if I move the mouse all the way outside of both objects (over the background) and then back onto the bottom shape, it does trigger the desired state change on the top object.
Anyone have any idea what's going on?
Are they grouped? I’m grouped objrcts the triggers often act as if they are on all objects in the group
Sent from my iPhone
No. They are single shapes.
-Rob
Hi Rob,
I jumped into your file and came across the same issue. It seems the mouse over trigger doesn't take effect until you're hovering over from outside the bottom box.
For your example, instead of adding the bottom box, why not select the Restore previous state when user hovers out in your top box trigger? I know that doesn't answer the question of how to trigger on mouse leave, but maybe that'll work in your situation!
I think this is a regression bug. I'm pretty sure I've used this technique in the past. And it seemed to work for other people on this thread. I'll submit it to support to get it on the bug list. This is pretty basic functionality and we've spent a lot of time trying to find a workaround.
We can't use restore previous state because we have three states and not two. Depending on the situation, we may need to skip the most recent state and return to the original. We could do this with "if" statements on actions if the mouseover worked on the underneath shape. I'm not aware of any other way to achieve this.
We've experimented with built-in state changes, but found they behave erratically or are designed in ways that don't make sense from a UX perspective. For instance, the rollover state takes precedence over the selected state. So if a user clicks an object to select it, they don't see the selected state until they move the mouse away from the object. There's no visual feedback that they made a selection.
Hi Rob!
That's a great step to take! We are looking into the issue with our Quality Assurance team. Thank you for bringing this to our attention.
This discussion is closed. You can start a new discussion or contact Articulate Support.