Forum Discussion
Overlapping States
I've been noticing a randomly occurring, but frequent, issue since the newest update. On some objects, the Normal/Original state will overlap with any other state (Hover, Visited, custom states, etc.)
So when you hover over a button, the text might change color, or an image might change, but the original text or original image can still be seen underneath.
Here is a quick example, a side by side screenshot from a published example:
On the Hover state, the icon is changed so that the bars on the chart sit a little higher when hovered over, though you can still see the original icon being used underneath when this happens. Additionally, you can see the stroke thickness looks more intensified as the images are overlapping. If I did this with a lighter text color on the hover state, and made it bold, you could still see bits of the original text peeking out from behind. I've tried testing this with .PNG, .SVG, .GIF, and other transparent files, but it happens with Storyline assets as well.
Here's another example using an icon built into Storyline. On Hover, the icon should just rotate 90 degrees, however, when in Preview or Published mode - the icon overlaps, and instead of having horizontal lines, we're left with a waffle/grid. Each example was made using a new Storyline file.
What's strange (or stranger) is that I can make a new state, set it to hover, delete all the objects on that new state, copy and paste in place the original assets used, and then swap the icon - and it will still happen.
The only workaround I have is to paste in place the base of the button (in this case the white rounded rectangle) two or three times, depending on any shape effects (e.g. drop shadows), which adding a bunch of objects to one state doesn't always yield the smoothest results once published. Additionally, in some circumstances, doing this causes a flicker effect on the hover state where the new button base flashes in before the rest of the other objects do, or the drop shadow will flicker when hovered over.
Fixes? Workarounds? Is this a known issue that needs to be patched?
Storyline 360x64 on Windows 11 Pro 24H2 26100.3194 on a new Lenovo P1.
Is there any solution to this? I'm using images+text as buttons with a disabled and hover state.
The hover state pops up, brightens, and gets a shadow.
The disabled state is darkened and has a different text color.
In both cases the "normal" state shows through, giving the darker text in the disabled state a white halo, and leaving a duplicate of the text/image too low in the hover state.
I'm also trying to do a similar affect with a gradient that changes color (no transition set), but the text and Normal gradient show through.
NormalHover in editorHover in Preview, blue tinge to pinkHover in preview with pop-up effectI'll also add that it took me almost an hour to post this because the website kept deleting my progress and few minutes, even after clearing cookies.
We feel your pain Andrew! Like others have suggested, you can try deleting the NORMAL state and create your own (different named) normal state, which has helped some of us avoid the overlaps, but you need to have triggers set up for anything that's not responding as it normally would.
I, too, hope this will get fixed soon!
Thank you!
How DO I delete the Normal state? It doesn't look like I can either rename or delete them.
Just FYI - I currently have an open ticket with Articulate Support that I believe has been escalated to it's highest after working on a course for one month and having my states completely break my timeline, wasting hours of my work.
I have specifically provided them this ticket to reference with this issue. I am praying with every fiber of my being that this issues sees its end soon. I cannot express my frustration with the amount of time I've spent redoing work enough.
This thread started 3 years ago. And this is not the only thread. Plenty of time to fix the problem. "Gathering votes"? My voice is very tired.
"Gathering votes..."
Jesus Christ. Abysmal.
The old trick of cutting and repasting into the state does not seem to fix this anymore. In my case I have multiple custom graphics as buttons, that have selected states that need text a different color so as to meet color contrast needs for accessibility. Since these are a button set using built in states, it fails. So it needs to be handled with multiple triggers and custom states in order to make it work. This has been a bug since Storyline came out, would be great if this was put higher up on the fix list. Thanks.
Thank you for sharing what you're experiencing regarding object states in Storyline, JeffForrer.
I understand how this can be a pain point for your development work. We're still gathering votes for this request so our product team can work on modifications.
We'll update this discussion once there are changes that might help, and you'll be among the first to know!
Forgive me for asking, but how is a development team gathering votes to fix a critical bug that has existed in the product for years and has caused substantial customer complaints? I do not mean that rhetorically, I am truly curious how this process works. We've all been asking for transparency from Articulate, and for some reason this issue receives little, which creates further frustration - which I hate to see, as I know you all are doing great work.
It's frustrating and bittersweet seeing things like Premium AI features being added to Storyline, when these features ignore years of customer complaints for efficiency and reliability. Perhaps with all the extra money being made from these newly added Premium AI features, Articulate could consider fixing it's cracked foundation? I truly don't mean any offense, but this support case alone has been open for almost four years.
This was never normal behavior and it's unfortunate that is how it's being presented now. There are a few other bugs with states that cause you to have to delete and restart the entire state. I truly hope those will not be considered "normal behaviors."
I am experiencing this issue as well. I have worked in Storyline for a very long time, and never encountered this before. I need a workaround, as I am on a very short deadline.
My normal state has a star shape added to it, and it is showing through in the other states. This is extremely frustrating. I have already wasted hours on this, and this is not billable time. I cannot expect my clients to pay me for issues due to the software.
Hello Carrie,
Thanks for reaching out!
Just to clarify the behavior you're experiencing, the built-in states by design are treated as a layer on top of the normal state, which means if an object from the normal state is not completely covered when a built-in state is shown, the object will be visible in the built-in layer. We have an open feature request to improve this behavior based on the feedback shared here in the community, and we'll let you know if there are any updates.
One way around this is to use custom states instead. I've attached a sample project file that compares the behavior of built-in states with custom states. You'll notice using custom states prevents objects in the normal state from appearing when a change state occurs.
This was certainly not normal behavior and it is unfortunate to think that is how its being presented now. There are more bugs within the states that actually require you to delete the state and start over when they happen, I truly hope these do not also get considered "normal behavior."
Hi folks,
I am having this same issue. It looks like the Staff here are more dedicated to finding temporary work arounds than an actual solution after 2 years of this ticket being active.
When will we stop being told to add Story files and submit tickets and finally have Articulate correct this behavior issue? Two years of Band-Aids is extremely unreasonable for your costs.
I have a case in support right now. Not much happening so far.
Hi Mike,
Thanks for reaching out. I see you've connected with my teammate, Gerald. You're in great hands!
Hello, does anyone solved this issue? Yesterday and today I worked on two different files from two different courses, and still facing this unexpected behavior :(
I attached an image where you can see a yellow border, wich should be the hover status, a green icon which belongs to Visited status, and a white mark behind the green icon which belongs to the Normal status :D
I'm using Storyline 64bit v.3.90.32893.0
I'm going to submit a new case attaching my file.
Thank you!
Hi Giulia,
I'm sorry to hear you've hit this snag!
It looks like you're working with Philam in a support case. We can continue the conversation there if you have any questions.
