Sticky hover state on a particular situation
Feb 15, 2016
Hi there,
I have a sticky hover state on a button only when a particular event happen;
--For design purpose we decided to go with custom submit button on quiz and default navigation for the course.--
That custom submit button has 3 states; normal, hover and down. The sticky hover state only happen if a learner forget to answer the question. The message box pop out, reminding the user to make a choice. After closing the message box, the state of the custom submit button stay on hover. Learner needs to hover over it again in order to reset the state.
I've been trying to included it in a button set (with only one button), set a trigger on itself to change state to normal once press, add a visited state, change the when revisiting condition of the slide to reset to initial state, nothing seems to work.
The message box popping is somehow blocking the next event.
Any idea? Am I missing something?
Best regards
18 Replies
Hi Richard!
Would you be able to share your .story file so that someone can take a look and further assist you?
Hi there,
I'll mockup something for tomorrow morning, since the original content can't be disclosed.
Is the hover state required?
Good morning, for some.
Find attached the .story file. Once again, when the learner makes no selection, submit and the Message box show up, it somehow jinx to the last state the button was.
Although not a show stopper, I usually craft every assets to its potential. The actual file will be revised by the client and we'll see from there.
It is in french.
Thanks!
Hi Richard! I apologize for the delay. I was able to see the behavior that you are reporting and wanted our support team to do a bit more digging. I have filed a case on your behalf. You should be hearing from someone soon and I will follow along as well.
Thank you Leslie,
I've already been contacted.
Its been a year developing with Storyline 2 and so far the greatest part is the dedicated community and staff we find in this forum.
Thank you again,
Best regards
Thanks Richard! I've shared your sentiments with the team as well :)
Hi Richard!
I popped in to check on your case and it looks like Wilbert has shared a solution with you :) Looks like buttons work better and perhaps you were utilizing shapes.
Hi there,
Wilbert did a great job at solving this issue with style!!!
A day without learning is not a satisfying day!
Thanks again!
Best regards
I've passed your sentiments on to the team Richard! Thanks for popping in to share :)
Having the exact same problem. I've tried using a shape and a button -- same issue. Could you share the solution? Thanks!
Hi Drake
can you share your file or even the slide you are having an issue with.
Which version of SL are you using?
Thanks Wendy. SL 2, update 11:1609.3020
Hi Drake
I get the same behaviour as you with the button not returning to normal state.
I created a new button and tried that. I also duplicated the built-in hover state. created a custom hover state, deleted the built-in state and used triggers to trigger to hover then trigger back to normal the custom state and it still doesn't work.
A previous fix that worked for me was to delete all other states i wasn't using e.g. down, visited, disabled and I tried that but still didn't work.
Perhaps upload to support and get Wilbert to wave his magic wand:-)
Sorry I couldn't be more help.
Wendy, you definitely gave it a hero's effort. Thank you! Will do.
Thanks Drake for submitting this as a support case. I see that you're working with Vevette on this particular case (# 01030637 for my reference) so I'll follow along as well and then I can update this forum thread once she's finished testing.
Hi guys,
On my side, it started wrong. I re-created a button ; taking a shape, creating states and so on. I should've taken a ready button and start from there. After taking a button to start with instead of a shape, everything was OK. No need for extra triggers or variables.
Thanks Richard for the update and glad it was as simple as that!
This discussion is closed. You can start a new discussion or contact Articulate Support.