thanks a lot for your expertise and creativity. I didn't think of the down state as a possibility to distinguish between the two steps of the event mouseClick (1. "mouseDown" and 2. "mouseUp").
MouseUp is then equal to a mouseClick. Now I have to find out how to simulate the event "mouseLeave".
I found a solution for the Event "mouseLeave", however not a very smart one:
Behind the object, the mouse pointer has to leave in order to trigger an action, is an invisible object of the same shape but sligthly bigger. This second object triggers the "mouseLeave" event by a simple mouseOver. As this second object is only visible when having hovered over the first object, it seems that leaving the first object triggers the action.
Hi Martin glad you got it sorted. I would use something similar for mouse leave , I would have likely left it visible and triggered on and off based on a variable, I find the hover/restore can be a bit flaky.
5 Replies
I am sure you could use the down state for mouseDown and possibly NOT down for mouseUp
Hi Phil,
thanks a lot for your expertise and creativity. I didn't think of the down state as a possibility to distinguish between the two steps of the event mouseClick (1. "mouseDown" and 2. "mouseUp").
MouseUp is then equal to a mouseClick. Now I have to find out how to simulate the event "mouseLeave".
I found a solution for the Event "mouseLeave", however not a very smart one:
Behind the object, the mouse pointer has to leave in order to trigger an action, is an invisible object of the same shape but sligthly bigger. This second object triggers the "mouseLeave" event by a simple mouseOver. As this second object is only visible when having hovered over the first object, it seems that leaving the first object triggers the action.
Hey, Martin! Clever workaround!
I'll let our team know you'd like to see a few more trigger actions in the trigger window: mouseDown, mouseUp, and mouseLeave. Thanks for the idea!
Hi Martin glad you got it sorted. I would use something similar for mouse leave , I would have likely left it visible and triggered on and off based on a variable, I find the hover/restore can be a bit flaky.
This discussion is closed. You can start a new discussion or contact Articulate Support.