Selected / Hover state - what about selected hover??

Hi Rob,

You don't need to create triggers for these as detailed here in the definitions of all the states, and how they'll behave. 

If you're having difficulty getting the states to work as detailed there, are you able to share a sample .story file with us here so that we could take a look at what you've got set up? 

Ashley, has this been solved? A "Selected-hover' state would in fact be a really great feature-add for Storyline. We use custom buttons/options for all of our courseware and this is an ongoing issue on my team as well.

Hi Jay,

I'm not sure based on Rob's description (as I didn't see his file) if he was using triggers or allowing the states to control themselves based on the definitions? There isn't a state that combines selected and hover if that is what you're looking for - but you're always welcome to share your thoughts in the form of a feature. 

Thanks for the response Ashley, I've sent the feature request sent, but this really needs a workaround in the meantime...

For example: We're using states to show selections of graphical elememnts that are in a custom marked quiz, and we're experiencing (and always have) the same issue that Rob described: When the user clicks the element, it doesn't appear to be selected until the mouse leaves the area. If the 'down' state is also used, the selection identifier (in this particular case is a checkmark) shows ONLY while the mouse button is down and this is confusing to learners. The flip side (that we've tried) would be to include the checkmark in the hover state, but then if the element is already selected and the user is de-selecting the element the checkmark stays there until the mouse leaves the region. Herein lies the NEED for a selected-hover state.

So, thoughts on a workaround?

Hi Jay,

Thanks for describing that fully here - it's really helpful and hopefully you included that in your request as well. I'll defer to our community of experts for other design solutions and workarounds. 

Lacking some genius input (and there are geniuses here), I think you are faced with a priority decision. Which is more important, hover or down and selected? My personal preference is to drop the hover, for what it's worth.

Hi, if you folks are still subscribed, I was hoping to get some clarification on what you're looking for. I feel like, if I understand this correctly it would be useful, just want to make sure I am on the same page.

I am attaching a story with a button with 4 states. Right now, I am not sure if you are: 

A.) Looking to create something like what is shown (due to the way hover works, which you can see bleeds into the down and selected states) ?

B.) Looking for a 5th state to be built in and available for that purpose, without the hover state bleeding in?

or C.) I still don't follow.

Thanks for the clarification.

Thanks Bill for sharing an example - even if they're not subscribed it may help others who come across this thread, so we always appreciate the examples. 

Hi Bill,

In our case, we're looking for "B" the 5th state that does not bleed through.

Regards,
Jay

That is correct Jay - B is what is missing.

And 5 years later, we still don't have a "Selected-hover" state. Why is this taking so long?

Hi Peter,

Since this discussion is older, let's revisit the default behavior in Storyline 360! Currently, a Selected state will show a "Selected/Hover" until you hover off the object.

Let me know if you're experiencing something different!