Just a small tip that has helped me. I used to solve this by using an additional element that was conditionally visible on hover, and that element’s visibility triggered the workflow.
That’s not necessary, as it turns out.
You can’t pick the Do When X is Hovered constraint in the workflow editor, but you can copy/paste it. I don’t know the reason this can’t be done directly, but it works nonetheless.
So just create the constraint in the visual editor, copy the expression and paste it into a Do When Condition is True workflow in the workflow editor, and voilá.
@josh
Is there a reason this is not possible to do in the “normal” way in the workflow editor, and is there any risk “hacking” it in this way? Will the loophole be closed, for example?
Thanks for this super useful info! Also:
When creating the expression in the Conditions tab, I found out that selecting “This Image is hovered”, pasting into workflows shows up “This customDefinition” instead. The workaround for this is to instead use “Image A” or something else, instead of “This ~~”.
@petter I think the loophole was closed. Just tried doing this as I have done it in the past and it is not working as it used to. Shame that it isn’t a built in option.
Thanks for posting how you used to do it, as I will use that method now.
Hey @Bubble! How do you suggest to make this simple. Here is why: we are building a Self “Help Mode” when any possible menu element and/or button is hovered. That should trigger a custom state for our Help Mode box that gets the help text from an specific help table. Thanks!
