Forum Discussion
How do button states stack?
I am making a collection of button templates in the style of my company's branding. In doing so, I want to make full use of the functionality that states in Storyline 360 provide, but am having troub...
I've done a LOT of work with button states and I've found that when something doesn't display correctly, there's usually a good reason. If I ran into a button display issue, and the resolution wasn't obvious, what I would end up doing is deleting the button altogether, and then recreating it from scratch. Simple enough. I'd be happy to look at this scene, and hunt down the issue alternatively. Could be there is left-over content that's not visible for some reason until the button is clicked. I've never head of states "overlapping," but there's likely unresolved formatting in the button state.
I've thought of a new way of phrasing my question that may help clear up some confusion:
Do states store all of the information about what they display, or only the parts that are different from the Normal state?
The first option would mean that when an object is in its Visited state, Storyline only displays the Visited state.
The second option would mean that when the object is in its Visited state, Storyline displays the Normal state and then applies the changes for the Visited state (in my example, it would change the font and fill colours).
I really appreciate your offer to help though. I've attached a story file with just the button in question. Following your advice, I recreated it from scratch (without the text boxes for each state), taking extra care to only edit the properties of each state that I wanted to apply when combined. However, the same thing happened as before, and only one state applies at a time.
Hello EmiledeKadt,
Happy to chime in!
You can think of the built-in states as states that are added as a layer on top of the normal state which would explain why elements from the normal state sometimes show in the other built-in states. One way around this is to add a background for the built-in state or use custom states for the interaction.
We understand the feedback from the community regarding how this behavior can be improved, and we're all tracking this through a report that gets shared with our product team. We'll let you know if there are any updates for this behavior!
