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 360

85 Replies

Spencer
Community Member
2 years ago
Hi,

It's almost a year and a half later since I first posted this topic, the issue is still present, and my go-to (temporary) fix is still the same: copy everything from a state (ie: Visited or Hover) with CTRL + A, delete it while everything is still selected, and Paste in Place (CTRL + Shift + D) on that same state. Again, this is an issue because it unlinks the states (which is part of why it works), BUT that means that any changes done to one state have to be manually done to the others individually, instead of updating automatically.

Another option is to use Custom states in lieu of the built-in states, and set custom triggers. That's my last resort, but it works consistently.

However, both of those fixes are time consuming, even if it's a minute or two. I've seen other people's fixes and still they're time consuming to some extent. That time adds up when you do it on every state, on every interactive object, on every slide, on every project. Being able to use/create states is a major function of Storyline, so I had hoped this would've been addressed more urgently or transparently, instead of seeing another comment about another support case being opened for the same issue we're all having. Though I do greatly appreciate the Articulate and Storyline team!

Is this on the radar to be fixed anytime soon?
BenoitDoidic172
Community Member
2 years ago
Solution currently is to make sure objects in different states completely cover up objects from the "Normal" state. I added a filled circle under the checkmark in your "Visited" state to fix your particular issue Dan.
Support.story1.7 MB
- DanLidholm-48cd
  Community Member
  2 years ago
  Hi Benoit, Thank you for the tip. I had already done that as a quick fix but this time I sent in to the forum/support. They shoild fix the problem, it's been around for a while.
- DanLidholm-48cd
  Community Member
  2 years ago
  Hi Benoit, I read your post a little to fast, but now I have just went through my email and read your post again. I did not solve it as you did. I just put an extra button on another layer. Your solution is much better. Really smart and easy, I will use that on every button. Thanks!
NickEastham-e77
Community Member
2 years ago
I agree with the above. This is not a new thing, Storyline has always done this. Would be nice if they would fix it.
JoseTansengco
Staff
2 years ago
Hi Katie,

Sorry to hear that you ran into this issue. I can confirm that I was able to observe the behavior on my end as well, and troubleshooting steps such as importing the slides to a new project file didn't help fix it.

We are currently tracking a known issue that causes non-normal state to show all objects from the normal state even if the non-normal state does not contain them. I went ahead and opened a support case on your behalf so we can verify if this is the same bug that is affecting you, as well as discuss possible workarounds for the issue. Thanks for raising this with us, and someone from our team will be reaching out to you shortly.

Hi Admin Qulturum,

It looks like you shared the same file as Katie's. If you're experiencing a similar behavior, please open a support case here so we can check what's happening.
LindaDickert
Community Member
2 years ago
No workaround? Anyone? Anyone?
BenoitDoidic172
Community Member
2 years ago
I can confirm this is still an issue, and is not expected behavior. What I see in Edit Mode does not matched the previewed or published course. I just submitted a case.

I thought perhaps it was because anything outside the initial bounds of the button shape are ignored, but my attempted fix (starting with an oversized white box, and placing all additional layer objects on top of it) also shows this bug, See sample here (Storyline file also attached): https://360.articulate.com/review/content/89fc3706-9f38-4161-a5b1-bc4b7f684c3e/review

button_state_overlap.story75.6 MB
- JoseTansengco
  Staff
  2 years ago
  Hello Benoit,
  
  Good call on opening a support case! I can see that my colleague Lianne is now testing your project file. You're in good hands, and we'll let you know about our findings through the support case that you opened.
BrettConlon
Community Member
2 years ago
Yep, it's really bad and needs to be fixed. I've also escalated a case and here's my sample button file that shows something different on each state. When the learner clicks the button you can see 3 overlapped states (Normal, Over and Down).

It's a complete mess!!!
TEST_Button_states-Overlapping_states.story120 KB
BenjaminCaul477
Community Member
10 months ago
I figured out a work around.

This happens only with the built in states. Create and edit custom states that do what you want, and they should alleviate the problem.
BethMcNamara
Community Member
10 months ago
I am having the same issue. this is such a basic function of Storyline, that my work has stalled...

I'd appreciate an updated response from Articulate to this issue. Rather than pushing each individual designer to support, please respond to this (and/or multiple other) posts about this issue with a solution. If none (yet), just let us know!
Spencer
Community Member
4 months ago
Is there any update on when this will be fixed? 770 days is a LONG TIME for a support ticket/bug report to be active and ongoing, especially with no transparency on when/how it is being addressed. I appreciate all that Articulate is doing, but it would be nice to get something more than just a request to submit another ticket, or told its still being looked into, etc. all these years later.