Forum Discussion
Overlapping States
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."