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?
I'll add my vote to that. There are many fixes that would help with accomplishing basic tasks in StoryLine and Rise that don't seem to be a priority. I guess it's not as sexy a selling point as AI.
Thanks for adding your voice to this feature request, Nick! I've updated the feature report with your comments.
Hi, having the same issue here. I have been using Storyline since it was released and this is the first time I am experiencing this.
The funny thing is that it happens with some elements, and some other is not. This erratic behaviour makes it so difficult to identify and correct, because it is not happening on preview mode, only when publised :(
Adding my vote here to have a solid look into this.
Thanks @spencer for the follow up.
Hello Victor,
Sorry to hear you're having issues with your project file related to overlapping states. It sounds like some random elements in your slides may be causing the issue for some objects but not for others.
Could I have you connect with us in a case so we can determine what's happening? Our support engineers may request a copy of the affected Storyline project to aid in the investigation. You can share it with them privately within the support case. We'll reach out soon after we hear from you!
Hi all
I also need to add a grievance to this list,
I added a layer and inserted a shape with specific text that is to display when the shape is in its normal state. I then created a unique state for this shape called 'Story' which displays another set of text. I set a trigger to change the shape state to Story when the user clicks, which it does but the text in the normal state also remains visible behind the story state text. I deleted the shape from the Story state and inserted a new shape and added the story text to this state. However when I test it the normal text remains visible behind the story state text!!(Edit: I see that other people have already suggested this, but I wanted to throw this out there anyway for anyone new to the thread.)
There may be a workaround using custom states. I was having the same issue when using Storyline's built-in states (hover, down, visited, etc.) and created a custom state with a trigger to simulate the built-in state I wanted.
Ex: The Normal state was overlapping the Hover state
My steps:
1. Create a new state by typing in a name different from the built-in options (Ex: Object Custom State)
2. Edit the custom state as desired
3. Create a trigger with the "Change state of" Action (In my case: "Change state of Object to Object Custom State when the user hovers over Object")
4. Select the "Restore previous state when the user hovers out" option
This showed no overlapping in Edit or Preview Mode
(From intern Anna Miller, working under Brandon Horn)
This is still happening and really causing lost time trying to work around or having to change my plans to allow for the bug... I've used shapes with states hundreds of times over the past 5 years and never ran into this until today...
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.
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!
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 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.
If you don't mind me mentioning, as the original poster, this was not 'normal' behavior several years ago when I reported the bug originally. It actively caused issues mid-project, which was what prompted me to open a support case, where Articulate staff acknowledged the issue and logged it as a "software bug".
Could you provide some context or history on the issue? I've been trying to find out information about my support case that's been open for over three years, but I'm finding out more information in Articulate's replies to other people's comments on my post than I am directly from Articulate.
I don't mean to come off as complaining! I believe some transparency would really help in instances like this! I don't mind if it takes several years for Articulate to address a bug, so long as its being addressed and I can see/know its being addressed. I get that Articulate has a lot of pots on a lot of stoves, and some things can sit on the back burner a bit longer. However, reading that the bug is now considered 'normal' behavior and the fix is now a 'requested feature' is a bit disheartening and confusing.
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."
