hover and down state don't end
Sep 16, 2015
Hi everyone,
the short of it: a click on a trigger starts a video in a lightbox. The video ends, the lightbox closes but the object with the trigger remains in hover as well as down state.
the longer explaination: I have to comment a user interface. I use a screenshot of the UI and points of interest are marked by colored boxes. For each box the hover state in addition shows a comment (text bubble) e.g. creating a fake mouseover that explains that feature. The mouse move off the box - the mouseover ends and so does the fake mouseover - all is well so far.
But some of the boxes trigger an additional short video for further explanaition - the videos are show in a lightbox and the lightbox closes when the video is through.
And here is the problem.
The lightbox closes but the trigger-box retains the down state and the hover state and with that the text bubble. It seems that Storyline just doesn't notice that the mouse has moved to another position.
I can end that mouseover by simply moving back onto the "hover area" and when the mouse leaves again the hover (and down) end.
As an extreme one could have six mouseover bubbles at the same time (and not be able to read most of them ...)
11 Replies
Holger,
If you post your .story file, someone here might look at it and be able to suggest a solution.
Hi, Holger -- I agree with Walt; a thorough description is always appreciated, but to truly understand and test the issue you are experiencing, it's a lot more helpful to look at the file itself. If there is sensitive material, you could always put together a sample file to illustrate the behavior you are encountering! :)
Walt, Christie,
you two are of course right and of course it is a case of "I would if I could but I can't" and so I did rebuld the problem. (And now I can even prove that I can listen to reason ;-)
Oh, and I have to correct myself - only the mouseover state remains on not the down state.
I'm baffled; somehow it is not reading the mouse position correctly. If it were, even the tiniest motion outside the trigger-box would be enough to trip the mouse leave event and change states when the lightbox closes.
A (probably not very satisfactory) workaround is to have each lightbox jump to the start slide when the timeline ends. It seemed to work better if I set the jump after the close trigger.
Hi Walt,
that's how I figured the problem to work (or rather not to work).
Thanks for the workaround.
It'sdefinitly a step in the right direction. I don't mind the setting of the additional trigger and it works structurally for me since I have indeed a seperate 1/4 second slide with all the jump points. But sadly it solves only half the problem because the problem is still present when the user stopps the lightbox manually.
Next best guess is to use a layer instead of a lightbox, if you can.
I would strongly encourage you to contact support with this, as I think it indicates a bug.
Hi, Holger -- If you would like for our Support Engineers to explore this issue further, please use this form to submit a case.
... done.
And thanks again for the help.
Certainly, Holger, and I will be on the look out for your case to follow along. :)
Christie, I appreciate that :-)
The problem is by now officially a bug and in the hands of te Quality Assurance. They can't give a timeframe and as soon as I get a solution I will post it here for further reference.
Thanks so much for your patience and the update, Holger. :)
This discussion is closed. You can start a new discussion or contact Articulate Support.