Hover State and Restore on Mouse Leave Issue - Behavior Reversed?

Hello all! This might be a pretty remedial question (I've only been using Storyline for a few days) and it's probably been asked before, but I could find anything on the topic in the last couple years so I thought I'd go ahead and ask.

I have a box with two states - Normal and Hover. Normal state also includes a 75% transparent "filter" positioned on top of the box to make the image on the box appear greyed out. Hover state removes the filter shape. I have a trigger set to change state to hover (no filter) when I mouse over the box and restore on mouse leave.  Probably not relevant, but a separate trigger shows a layer when the user clicks on the box.

Initial state is loading in as designed (Normal) but then on the first mouse-over, nothing happens. When you move the mouse away, it goes to the hover state and returns to normal state on subsequent mouse-overs. So the behavior stalls until an initial mouse over and then the behavior is reversed from that point forward.

Any suggestions as to why this is happening?

Slide is attached. There are some animations on the slide since I will eventually load in some audio, but nothing involving the boxes.

I've already tried adding a disable state until after the animation completes and adjusting the box timeline to not appear until after the animation completes, since one post seemed to indicate that animations were the issue, but neither approach made any difference.

3 Replies
Walt Hamilton

Blake,

Lot of things going on here.

Built-in states (their names are in the drop-down when you name a new state) come with their own triggers. When you create hover state, it automatically has a built-in invisible non-editable trigger to change to hover when mouse hovers over. Writing your own trigger will conflict with the built-in one. While unpredictable and sometimes spectacular, the results of the conflict are seldom pretty.

Groups and states do not play well together. Ever.

The hover state really is an overlay. It leaves the previous state as is, and attempts to shade or color it.

States are more fragile that you suspect, and complicated things (like picture fills of objects) may well confuse them.

I like your idea, and in the attached sample the Wireless example works. I saved the clear picture as a picture, loaded it into a graphics program, and saved a clear version, and a shaded version. I loaded the shaded version as the original shape, edited the states and created a Hover. I deleted the picture and loaded the clear version for the hover state.

Blake Hylton

Thank you both for the insights! Thank you Walt especially for the tips embedded in your response and the working process! It looks like I have it working as intended now, by following Walt's feedback with inserted images (rather than image filled objects) and doing the image manipulation in a separate graphics program. Plus of course Wendy's very appropriate point that the built-in Hover state doesn't need a trigger!