I have built a slide with buttons (each leads to a different scene) and each has a Normal, Hover and Visited state. Once a button has been clicked I want it to still be clickable but for the hover image to stop appearing. Any help would be very appreciated!
Hmmm, doesn't seem like there's a straightforward way to do this. You may have to build some sort of workaround where you Hide the button after it's been clicked and Show a button in the same spot (and of the same size) whose States are designed the way you want them. Or, put these 'second' buttons on layer(s) and have the layer(s) appear after the 'first' buttons [on the Base layer] have been clicked.
Danica, one option is to create your own Hover state and call this state based on the condition that the button' state is Normal (meaning is hasn't been clicked yet). See attached a quick example.
I'd agree with Michael here - that creating your own hover state would allow you more flexibility in terms of determining when to show it based on conditions and using the regular "when mouse is hovered over" trigger.
I would suggest also that you don't use the built in hover state. Creat your own called hover1 or something. Then use triggers with conditions to decide when it gets a hover state or not.
On the project I'm working on I've got buttons that are hidden to start and then become normal after the previous button is selected. If none of your buttons are hidden to start, then you only need the first trigger. If your buttons are hidden you will need two triggers, as follows for each button.
First Trigger:
Action: Change state of
On Object: (button)
To state: Visited
When: Mouse hovered over
Object: (button)
On Condition: (button)'s state is visited
Second Trigger:
Action: Change state of
On Object: (button)
To state: Normal
When: state
On: all of (select the previous button, the one that must be visited before the hidden button can change)
Is: Visited On Condition: (button)'s state is Hidden
Both of these triggers must be in order and before the trigger to jump to any given layer or slide. You must also uncheck the Restore on Mouse Leave option.
This may sound a bit confusing so if you have any questions please let me know!
Hi Articulate, has there been an update to this? We're experiencing this same issue in a course that repeats the same button 80 times, so the manual workaround seems daunting. Thanks!
Hi Bobbi! This thread is a bit dated, but did you create your own hover states as was advised in this thread? Are you asking if we updated the way the built-in hover state works?
This article explains how the built in states work.
We used the button that is native to Storyline. However, it appears a hover state is being applied to the VISITED state. The visited state is gray with black font.
We have four of the same button on each page (they were formatted, then copied and pasted). Once the button is changed to the VISITED state, hovering over the button turns the font white for two of the buttons. One stays black. And the last one has one word in black and one word in white. (I'll try to get a screen capture that shows this.)
What we don't understand is why the formatting of the button is changing once it's already in its VISITED state.
Thank you for your assistance, Leslie. I've attached a document that shows the HOVER state issue for buttons that are in their VISITED state. I hope it helps to clarify the issue. I'd love to know your thoughts on what could be going awry. The fact that we copied the button but each button shows a different behavior has us befuddled.
I have noticed that as well, using format painter to format buttons states doesn't always change the font colour and you have to go into each one individually and change it
That's the thing, though. They're all formatted correctly. It has something to do with the Hover state applying itself to the Visited state, but for the life of us, we can't figure out how to fix it. Is it possible to "turn off" the Hover state when a button is in the Visited state?
if I find I have an issue with an inbuilt state - I create my own - delete the default ones and then use triggers to control.
Have you tried creating a new project file and importing your current file in - maybe there is something glitchy...or if you want to upload your .story file - someone here might be able to cast a fresh set of eyes over to see if anything pops out.
We'll try the import route and see how that works. Thank you for the recommendation!
Unfortunately, we're unable to publicly share this course, but I'll see if we can post a couple of slides as an alternative. I appreciate your time and ideas, Wendy. Thank you so much!
Thanks for sharing the screenshots here. It was helpful to see what you're describing, but I think we'd also need to see the way the states are set up and what occurs when we copy one of your buttons as well. If you're able to share even just that one slide it would be incredibly helpful. You can attach it here using the "add attachment" button or as Wendy said send it along to our Support team and they can sign an NDA if needed. I'd also agreed with Wendy's recommendation of importing it into a new project to see how it behaves there. You can follow the steps here for importing.
The hover state would only not show as a default if the button were in the disabled state, per the definitions of the built in states here.
Thanks for sharing the .story file. I didn't see anything off in the way the buttons were created, but I was able to copy and paste the one working button and recreate the others and then they behaved as expected with the black text. This is uploaded for you below.
You'll want to review the other information I shared in regards to working on local project files, and let us know if odd behavior persists in your file.
23 Replies
Hmmm, doesn't seem like there's a straightforward way to do this. You may have to build some sort of workaround where you Hide the button after it's been clicked and Show a button in the same spot (and of the same size) whose States are designed the way you want them. Or, put these 'second' buttons on layer(s) and have the layer(s) appear after the 'first' buttons [on the Base layer] have been clicked.
Thanks for the idea Bob! I am going to try creating a new button and hiding the old one after it has been used.
Hi Danica, I had kind of a similar situation, not exactly the same, but similar where I needed to duplicate the object and create different hover states for each. I wrote a blog about how I did it if that will help you:
http://dansweigert.wordpress.com/2014/03/10/hiding-the-quiz-until-the-end/
Danica, one option is to create your own Hover state and call this state based on the condition that the button' state is Normal (meaning is hasn't been clicked yet). See attached a quick example.
Hi Danica and welcome to Heroes!
I'd agree with Michael here - that creating your own hover state would allow you more flexibility in terms of determining when to show it based on conditions and using the regular "when mouse is hovered over" trigger.
Danica,
I would suggest also that you don't use the built in hover state. Creat your own called hover1 or something. Then use triggers with conditions to decide when it gets a hover state or not.
Good luck,
Tim
Hi Danica,
On the project I'm working on I've got buttons that are hidden to start and then become normal after the previous button is selected. If none of your buttons are hidden to start, then you only need the first trigger. If your buttons are hidden you will need two triggers, as follows for each button.
First Trigger:
Action: Change state of
On Object: (button)
To state: Visited
When: Mouse hovered over
Object: (button)
On Condition: (button)'s state is visited
Second Trigger:
Action: Change state of
On Object: (button)
To state: Normal
When: state
On: all of (select the previous button, the one that must be visited before the hidden button can change)
Is: Visited
On Condition: (button)'s state is Hidden
Both of these triggers must be in order and before the trigger to jump to any given layer or slide. You must also uncheck the Restore on Mouse Leave option.
This may sound a bit confusing so if you have any questions please let me know!
Thanks,
Rose
Thanks Rose for the explanation and helping out - welcome to the Heroes community!
Hi Articulate, has there been an update to this? We're experiencing this same issue in a course that repeats the same button 80 times, so the manual workaround seems daunting. Thanks!
Hi Bobbi! This thread is a bit dated, but did you create your own hover states as was advised in this thread? Are you asking if we updated the way the built-in hover state works?
This article explains how the built in states work.
We used the button that is native to Storyline. However, it appears a hover state is being applied to the VISITED state. The visited state is gray with black font.
We have four of the same button on each page (they were formatted, then copied and pasted). Once the button is changed to the VISITED state, hovering over the button turns the font white for two of the buttons. One stays black. And the last one has one word in black and one word in white. (I'll try to get a screen capture that shows this.)
What we don't understand is why the formatting of the button is changing once it's already in its VISITED state.
Ah, yes please Bobbi. Perhaps I didn't fully understand what you were asking then.
Thank you for your assistance, Leslie. I've attached a document that shows the HOVER state issue for buttons that are in their VISITED state. I hope it helps to clarify the issue. I'd love to know your thoughts on what could be going awry. The fact that we copied the button but each button shows a different behavior has us befuddled.
Hi Bobbi
I have noticed that as well, using format painter to format buttons states doesn't always change the font colour and you have to go into each one individually and change it
That's the thing, though. They're all formatted correctly. It has something to do with the Hover state applying itself to the Visited state, but for the life of us, we can't figure out how to fix it. Is it possible to "turn off" the Hover state when a button is in the Visited state?
Hi Bobbi
if I find I have an issue with an inbuilt state - I create my own - delete the default ones and then use triggers to control.
Have you tried creating a new project file and importing your current file in - maybe there is something glitchy...or if you want to upload your .story file - someone here might be able to cast a fresh set of eyes over to see if anything pops out.
That's not the answer we were hoping for-LOL! This button appears 80 times in the course.
Yikes...
We'll try the import route and see how that works. Thank you for the recommendation!
Unfortunately, we're unable to publicly share this course, but I'll see if we can post a couple of slides as an alternative. I appreciate your time and ideas, Wendy. Thank you so much!
Sure Bobbi - good luck and maybe log a support ticket and upload to Articulate - they can sign an NDA if you need it.
Hi Bobbi,
Thanks for sharing the screenshots here. It was helpful to see what you're describing, but I think we'd also need to see the way the states are set up and what occurs when we copy one of your buttons as well. If you're able to share even just that one slide it would be incredibly helpful. You can attach it here using the "add attachment" button or as Wendy said send it along to our Support team and they can sign an NDA if needed. I'd also agreed with Wendy's recommendation of importing it into a new project to see how it behaves there. You can follow the steps here for importing.
The hover state would only not show as a default if the button were in the disabled state, per the definitions of the built in states here.
Here's the storyline file to show you the buttons.
Hi Rebecca,
Thanks for sharing the .story file. I didn't see anything off in the way the buttons were created, but I was able to copy and paste the one working button and recreate the others and then they behaved as expected with the black text. This is uploaded for you below.
You'll want to review the other information I shared in regards to working on local project files, and let us know if odd behavior persists in your file.
This discussion is closed. You can start a new discussion or contact Articulate Support.