We created an image-driven "hub* menu with "Complete" states, (image + tick).
All worked fine until you (accidentally) hovered the mouse over the custom Complete state, and it automatically went BACK to "Hover" state, then stayed there when mouse removed.
Is this a (known) issue?
Think I saw this a long time ago, but not seen recently. Got rid of it by deleting the "Hover" state, but that's not idea.
I didn't know if it was appropriate to resurrect this old post or to start a brand new one. Bruce's original question is what I'm running into now. I have four states in total. Normal, Visited1, Hover Visited, and Hover1. The slide starts with the object on Normal. When the learner hovers mouse over we have a larger version of the image so it looks like hover is making the image bigger slightly. When the learner clicks a layer displays. A trigger (we tried both on the layer and attached to the hotspot on the base layer) tells the state to change to Visited1 when clicked and a condition on a separate mouse over trigger changes state to Hover Visited on mouse over. Our problem is that Hover Visited overrides the "Visited1" state so when the mouse is moved off the original "Normal" state is back again.
Anyway to keep the Visited state after mouse over? What am I missing?
Oh, and to add another layer of complexity, since the item is a strange shape we've used a freeform hotspot to trigger everything off of rather than the base image.
I'm attaching a sample of what I'm trying to achieve. It's not my actual file since I can't share that. The only difference with this file is I've triggered everything off of the object (square) instead of a freeform hotspot.
Anyone have any thoughts on how I can achieve this? Do I really have to get rid of my hover states?
Our records show that Bruce's original problem was resolved
with the release of Storyline Update 1 in 2012.
It looks like you are explicitly changing the object's state
to HoverVisited via a Trigger (based on a variable). This makes
sense since there isn't a built-in HoverVisited state, but it also
means that the object loses its Visited state at that point.
As one alternate approach that might achieve what you're
seeking, within this .story project file I drew a Freeform hotspot to
cover all white space around your object, then added a Trigger to Change
state of Rectangle 1 to Visited when the user hovers the mouse over
Hotspot 1 if SquareVisit is equal to True and made sure to deselect Restore
on mouse leave. I'm sure the Super Heroes within this Forum Thread can
think of better alternatives as well.
Our records show that Bruce's original problem was resolved with the release of Storyline Update 1 in 2012.
It looks like you are explicitly changing the object's state to HoverVisited via a Trigger (based on a variable). This makes sense since there isn't a built-in HoverVisited state, but it also means that the object loses its Visited state at that point.
As one alternate approach that might achieve what you're seeking, within this .story project file I drew a Freeform hotspot to cover all white space around your object, then added a Trigger to Change state of Rectangle 1 to Visited when the user hovers the mouse over Hotspot 1 if SquareVisit is equal to True and made sure to deselect Restore on mouse leave. I'm sure the Super Heroes within this Forum Thread can think of better alternatives as well.
Good luck with your project!
I think this might be the best way - a visitedhover would make a good feature request.
Thanks for the replies guys. Justin, in this case, since we need to have multiple images involved around the initial one for the rest of the diagram, I think we'll just remove the hover visited state altogether. I just tested that and it works very well (other than not showing the hover visited that is).
As always you guys are great! Thanks for the help and for letting me highjack the post!
34 Replies
The great Sir David,
Once again to help us...I needed exactly that...I am so impressed!
Thanks a lot...I cannot wait anymore to implement it in my project .....
Thanks once again!
I like that
But seriously, I'm glad that solution works for you.
Hi everyone,
I didn't know if it was appropriate to resurrect this old post or to start a brand new one. Bruce's original question is what I'm running into now. I have four states in total. Normal, Visited1, Hover Visited, and Hover1. The slide starts with the object on Normal. When the learner hovers mouse over we have a larger version of the image so it looks like hover is making the image bigger slightly. When the learner clicks a layer displays. A trigger (we tried both on the layer and attached to the hotspot on the base layer) tells the state to change to Visited1 when clicked and a condition on a separate mouse over trigger changes state to Hover Visited on mouse over. Our problem is that Hover Visited overrides the "Visited1" state so when the mouse is moved off the original "Normal" state is back again.
Anyway to keep the Visited state after mouse over? What am I missing?
Oh, and to add another layer of complexity, since the item is a strange shape we've used a freeform hotspot to trigger everything off of rather than the base image.
I'm attaching a sample of what I'm trying to achieve. It's not my actual file since I can't share that. The only difference with this file is I've triggered everything off of the object (square) instead of a freeform hotspot.
Anyone have any thoughts on how I can achieve this? Do I really have to get rid of my hover states?
Good Morning, Leah.
Our records show that Bruce's original problem was resolved with the release of Storyline Update 1 in 2012.
It looks like you are explicitly changing the object's state to HoverVisited via a Trigger (based on a variable). This makes sense since there isn't a built-in HoverVisited state, but it also means that the object loses its Visited state at that point.
As one alternate approach that might achieve what you're seeking, within this .story project file I drew a Freeform hotspot to cover all white space around your object, then added a Trigger to Change state of Rectangle 1 to Visited when the user hovers the mouse over Hotspot 1 if SquareVisit is equal to True and made sure to deselect Restore on mouse leave. I'm sure the Super Heroes within this Forum Thread can think of better alternatives as well.
Good luck with your project!
I think the saddest thing is that I do not even remember submitting that original bug, or which client it was! :(
I think this might be the best way - a visitedhover would make a good feature request.
Could it be your client that makes the fizzy drinks by any chance?
Thanks for the replies guys. Justin, in this case, since we need to have multiple images involved around the initial one for the rest of the diagram, I think we'll just remove the hover visited state altogether. I just tested that and it works very well (other than not showing the hover visited that is).
As always you guys are great! Thanks for the help and for letting me highjack the post!
Leah
Thanks for the update Leah and I'm happy to hear you've got it working now!
This discussion is closed. You can start a new discussion or contact Articulate Support.