Hover State...bug?

This normally happens if you have a custom state and hover state and open a layer, when the layer closes the hover state seems stuck on.  Doesnt happen every time but there is some strangeness in states

I have also found some strangeness and get around it by being careful to give all states a custom name rather than using "Hover" etc. which seem to be in-built / reserved names.

It's counter-intuitive to me not having "mouse out" events to make sure I clean up if anything gets sticky, but I can see why - with HTML 5 on mobile devices there's simply no mouse, so there's no hover... or mouse out... or mouse in...

Hi Justin,

As Phil says - it does not happen every time, but it was pretty embarrassing yesterday...

I cannot send you the file as we had to delete the "Hover" state to make it work. When something like this happens, my first reaction is to try and protect the integrity of the product I am demonstrating, and my own professionalism, so I'm afraid saving a copy off client PC to send in is not at the top of my list! 

The scenario is simple, and always the same ((in my experience)

1> A slide has a series of buttons, each of which have (as Phil said...) a Custom state called "Completed" (for example).

2> The state just has a tick on the button (for example)

3> A T/F variable is set at the start of the course

4> Clicking the button shows a Layer (or another scene), and then at the end, the next button swaps the Variable to "True", and then moves back to the menu.

5> A "When Timeline <on slide> starts" Trigger sees the variable is True, and displays the Custom State for the "completed" section.

6> Hovering over the new State "locks" the button into Hover mode, removing the tick, and you cannot get it to go back to Completed.

Hope this helps.

Bruce

Thanks for the additional level of detail, guys.  I am passing this information on to the Articulate QA Team.

Hi guys,

If you have a project where you can reproduce the issue, please provide a link to it.  I'd like to do some additional testing in this area.

I was going to suggest deleting the hover state (but I guess you did that already)  - if you want a hover state try creating a custom one. You will then have to add a trigger that has to display it on mouse over but you should be able to add a condition that then stops this from occuring when the object is selected.

Sorry Brin, I dont have any projects that still have that problem in, I just find a work around when it happens

Hey guys,

Not sure if this is a bug or I am missing some important logic of states.....

When I drag a button should it show me 'hover' state or the 'down' state ? My button strangely shows both!

You may have a quick look of my states: http://www.vinayakkadam.com/samples/drag_hover_output/screenshot_states.jpg

Published version: http://www.vinayakkadam.com/samples/drag_hover_output/story.html

Source Story: http://www.vinayakkadam.com/samples/drag_hover_output/drag_hover.zip

Your thoughts please ?

As ever,

VK

I think this is expected although strange behaviour, although why you would have a down state on a drag item is beyond me

I have a callout on hover state and when I start dragging the drag item I do not want the call out to appear ? Can you tell me any other way around ?

Secondly can you please answer specifically my 1st question please....When I drag a button should it show me 'hover' state or the 'down' state ?

Thanks for your kind consideration!

As ever,

VK

As I said I think this is expected behaviour with hover and down, not saying it is right but likely expected.

I dont know why you want to drag a button from a UI point of view it is just wrong users expect things to work a certain way.  I cannot really think of an elegant way to get rid of the callout, it would really be a kludge that would break at some point

I want to drag a button because:

I have 4 drags and 4 drops and every drag has an explanation (seen on rolllover) and based on the explanation user has to drag and drop on the correct target ? If user drops incorrectly drop has to return back to its original position. If teh user drops correctly drag should be disabled.

Can you tell me is there any other that you understand on top of what I am trying to do which you do not understand ?

Dragging buttons is wrong, you can add callouts to any other shape or object but using buttons is not right (maybe its just me).

Users expect buttons to be pressed not dragged, 

I strongly believe we should be building intuitive designs, this would save us time explaining how to use the course.

The problems you have are because of this, you may be best deleting the hover state and the down state because you dont need the down state

"Users expect buttons to be pressed not dragged"

How come looking at an element on screen user would come to know is it a button or shape ? Even if I use shape I get the same issue.....

I am very sorry but I feel that my question is still unanswered. If user click and drags a shape which state should it be in....hover or down ? Can somebody please answer this basic question ? I am not able to make out .....In my opinion it should be in 'down' state ?

Buttons have specific elements that make them buttons, gradients, drop shadows, down states.  You could make objects that can be dragged that do not have these element.

A dragged shape could, if you wanted, have a custom "Drag" state, but it is not "Down" per se. "Down" is a non-moving state, or at least moving in one plane, not across the screen at all.

Phil is correct - drag items, not buttons. Standard GUI development guidelines/protocols should be followed.

Bruce

Hi Bruce and Phil,

Thanks for the explanations...thats helped to make my basics strong....please dont get irritated by me questions...My only intention is to get my basics right....coming back to the issue I am facing....

I just took a shape and

- assigned some drag action to it

- added a callout in the hover state

- gave a blue color to my shape in down state

Now when I rollover I see the callout but when I drag I see both the callout and the down state ? I just wanted to clear my basics more.....should It be displaying both the states or just down state ? Is it a Storyline bug or expected behaviour ?

I don't see the need for a down state, it is not a button.

I think that it is probably expected behaviour that down and hover are visible but this is strange.

You could add a change state trigger when object dragged over to clear out the down/hover

My requirement is:

- When user hovers it should show a callout

- When user starts dragging, call out should hide....

Can you tell me is this possible in Storyline ? Adding a trigger on drag event does not changes the state of shape....I think I cannot override the default behaviour!

Hi Vinayak -

You can do what you're looking for if you make the hover graphics a single image. Take a look at the attached file and you'll see it's completely possible to create a unique hover effect for your objects while maintaining a down state while dragging.

Preview

That is nice David, put a fade on that hover so it doesnt come in so abruptly

Is that a texture or gradient background

Did you just edit and add the file!

I updated the published version to include a disabled state. I think it seems strange to have the hover active after dropping on a state.

But the main thing is to use a single image for your combined drag button and hover objects.

Updated story file attached.

@phil - I didn't get all fancy schmancy with a faded hover state. But that's a good idea and it should work.

I did update the story file, yes.