Why don't you try deleting the regular Hover state? That'll prevent its built-in functionality from interfering with your custom mouse-over triggers.
I will give that a go again but the client still ants the hover. But let me try it again. Cheers for the reply
If the clients wants a "regular" hover state (in addition to the UserA and UserB hover states), you could create a custom hover state that looks like the regular built-in one.
In that case, I'd use a text variable to track which state to show. For example, start the variable with a value of "regular." When the user indicates they are in the "A" path, adjust the variable to "userA." When the user indicates they are in the "B" path, adjust the variable to "userB." (You could also use a number variable, and assign values as 1, 2, or 3.)
Then have 3 triggers, each of which would show the appropriate state on mouse-over based on a condition that checks for the right variable value.
