I am trying to make a set a flashcards on my slide that have icons on the front and text on the back. I created the shapes and added them to a button set. For each shape, I have a normal and a selected state, and when I look in the States window, it looks right. There is just the icon in the normal state, and just the text in the selected state. However, when I preview the slide, the icon remains over the text when I click on the shape, so I can't read the text. I included two screenshots. If you can let me know what's wrong or if there's a better way to accomplish this, that would be great!
This looks like a bug based on the screenshot and the reported behavior. Would you be willing to share a copy of your project file here or in private by opening a support case so we can verify this for you? We'll delete it when we're done testing!
Thanks for reaching out and I'm so sorry to hear that you're experiencing this as well! If you're comfortable sharing your file with our team, I'd be happy to take a closer look at what's going on. You can upload it here or privately in a support case. We'll delete it from our systems once troubleshooting is complete!
Great move on opening a support case and sharing your file with our support engineers! It looks like my colleague Luiza tested your file and was able to reproduce the issue where the 'normal' state of an object persists through other states. I see that Luiza replied to your e-mail with some feedback and workaround steps you can try while our team looks into this issue further.
Depending on priority and risk, some bugs can be fixed quickly, while others take longer to resolve. For your reference, here's a closer look at how we identify and tackle bugs.
We'll be sure to keep you apprised of any news or developments regarding this issue and can continue this conversation over in your support case.
We don't have a public document for the workarounds of this issue. But, in addition to what Nedim suggested above, I'd like to share a list of workarounds that worked for some users. They might be helpful to you as well:
Remove the shape or objects from the Normal state that persists in the the other states.
Imagine that when editing the other states, the other objects from the Normal state are there. You'll just need to edit and overlap the state's objects with themselves to effectively "hide" the objects from the Normal state.
Instead of inserting a textbox on the Normal state of a shape, just paste/type the text directly on the shape. The text will initially carry over to the other states, but deleting or replacing that text with another text will resolve the error.
If you need help applying the workarounds to your Storyline project, you can upload the project file here or privately in a support case so we can take a look. We'll delete it when we're done!
Again, this has worked for years. I asked for an update on this and here's Articulate's reply:
"We've determined that it's expected for the objects in the 'normal' state to persist in the other states because Storyline treats the latter as layers on top of the 'normal' state. As a result, the other states are adornments of the 'normal' state. Because of this, we've considered this a feature request instead of a software bug."
Basically they are turning a bug into a feature request.
10 Replies
Hello Marissa,
Sorry to hear that you ran into this issue.
This looks like a bug based on the screenshot and the reported behavior. Would you be willing to share a copy of your project file here or in private by opening a support case so we can verify this for you? We'll delete it when we're done testing!
This is happening to me as well - and others on my team.
Hi, Nicole!
Thanks for reaching out and I'm so sorry to hear that you're experiencing this as well! If you're comfortable sharing your file with our team, I'd be happy to take a closer look at what's going on. You can upload it here or privately in a support case. We'll delete it from our systems once troubleshooting is complete!
Done.
How many support cases and files are needed before it's determined to be a bug and fixed with an update? Thanks!
Hi Nicole!
Happy to share some insight on this!
Great move on opening a support case and sharing your file with our support engineers! It looks like my colleague Luiza tested your file and was able to reproduce the issue where the 'normal' state of an object persists through other states. I see that Luiza replied to your e-mail with some feedback and workaround steps you can try while our team looks into this issue further.
Depending on priority and risk, some bugs can be fixed quickly, while others take longer to resolve. For your reference, here's a closer look at how we identify and tackle bugs.
We'll be sure to keep you apprised of any news or developments regarding this issue and can continue this conversation over in your support case.
We are having the same issue. Is there a public document with work arounds?
Work around: click on the selected state, cut all objects and paste them back while you're still in the selected state. Attached illustrated video.
Hi Winthrop University,
We don't have a public document for the workarounds of this issue. But, in addition to what Nedim suggested above, I'd like to share a list of workarounds that worked for some users. They might be helpful to you as well:
If you need help applying the workarounds to your Storyline project, you can upload the project file here or privately in a support case so we can take a look. We'll delete it when we're done!
This used to work and now it doesn't. Why the "work arounds" and not a fix?
Again, this has worked for years. I asked for an update on this and here's Articulate's reply:
"We've determined that it's expected for the objects in the 'normal' state to persist in the other states because Storyline treats the latter as layers on top of the 'normal' state. As a result, the other states are adornments of the 'normal' state. Because of this, we've considered this a feature request instead of a software bug."
Basically they are turning a bug into a feature request.