Forcing the disabling of the hover effect ?
Sep 14, 2018
Hello,
I have a problem using different states of an object in a drag and drop context.
Explanations.
I have a three-state object:
1) Normal - the initial state of the object
2) Small - the small version of my object when it is moved to the drop box.
3) Label - A state where a small label appears above my object to say what it is. I didn't use the pre-built hover state, because it caused more problems (like a kind of loop between two states).
I want my object to change to the "label" state when the mouse hovers over the object. It works with a trigger.
Then I want my object to reduce (go to the small state) when it is moved to the drop box. It works with a trigger.
But however, all the methods I have used to prevent the hover effect after moving the object (triggers, variables, conditions) do not work.
When the object is moved (and therefore small), it returns to its "normal" state (and not the "label" state) as soon as the mouse is over it. But more importantly, it remains in this state once the mouse comes off it.
Is there a way to force the disabling of the hover effect?
See attchement for more details.
Thanks for your attention.
6 Replies
Change the state to disabled?
Thanks!
It would be a solution if my goal was to drag an item in a drop box. But here, my item can be dropped in 8 boxes. 4 are correct and 4 are wrong. So the learner must keep the possibility to drag it back and drop it in another box.
Plus, as I got a label state, this state is displaying when an object is set to disabled state, and I would like to avoid this default behavior.
I think the problem is that you have a conflict in execution.
When you drag the shape, you are activating the hover trigger (label) which has a command to restore upon leaving. And you also trigger a change to the object's state (petit) when dropped but still haven't left the object.
Thus, it's changing the state when dropped (based on the drop trigger) and then it's also changing the state when you leave (based on the restore) but it's not picking up the condition because when you started the drag it was till the initial state and not in petit.
Thanks, Tom.
That's right.
Is there a better way to achieve my desired result?
A few ideas
I wanted to try the 3rd which seemed to me to be the most successful idea to get a homogeneous result, but I was afraid to create other problems later on with the layer set, because I will still add two layers per item each time, to tell the learner when the placement is correct and when it is incorrect.
So I'm going to test this solution and see what it can do.
Thank you for enriching my thoughts.
This discussion is closed. You can start a new discussion or contact Articulate Support.