Forum Discussion
[BUG] When initial state is set to "Disabled", the style pasting gives it normal state styling
Hello,
This is present for quite a time already, but never really bothered me as I rarely used that, but today I've noticed it also breaks with another case... however, here is the problem:
1. I make button with style normal and disabled (which has for example different background or text or something).
2. I copy that button to some screens across the whole project.
3. Some of my screens have button initially disabled (initial state set to disabled) and they unlock after some activites.
4. I've changed my mind and altered the normal or disabled state of original button and now I want to copy it's style (ctrl+shift+c) to all the other buttons (ctrl+shift+v).
5. When pasting style to another button with initial state: disabled, storyline ignores the disabled state styling and gives it the normal state styling.
This occurs on fresh and already existing projects since... forever I guess :)
Well, not a big deal at all, but now I have situation when I'm translating one project to 10 different languages, and I have used images for buttons. I have different image for normal and disabled style. I've replaced it with media library. I had exactly 114 images of "normal" image and 114 images of "disabled" image. After replacing, I have 163 normal images and only 65 disabled images. Now I need to manually change 49 buttons*10 translations = 490 buttons. And of course, check the steps above, I cannot use "ctrl+shift+c" to paste style. I manually need to enter state editing for 490 elements and manually replace the image.
Can this be somehow addressed in future update? I think that's not intended behavior.
Hello Mateusz!
Thank you for sharing the steps you've taken! I took the same steps and am also seeing the style of the Normal state carry over to the additional states, which also includes the disabled state. I've connected with my team and determined this is actually not a bug since the style of the Normal state always carries over to additional states. If you'd like a different style, you might consider adding a new state and not using the Normal state.
That's not even close to what I'm talking about. I know that normal state carry over and that's perfectly fine. It would be strange it it doesn't.
When you set initial state of any object to disabled and then try to change states and styles of that object, it doesn't carry over the disabled state style, but switches it to normal state style, but stays 'disabled'.
I have 100 buttons set to initial state disabled. These buttons are images, every state has different image. When I change with media library the image, it magically becomes the normal state image instead of disabled state image if it has been initial state: disabled. It just switches. Basically my whole navigation is destroyed and for you that's intended? When I use state disabled and I want to change that style with the easiest possible way, e.g. copy&paste styles or use image replace function in media library, I don't want it to magically become 'normal' state image now.
If that's truly intended, why doesn't state visited or hover doesn't also change? :) It's a bug Lauren and the bug is, when you use "initial state: other than normal" function, Storyline treats it as normal instead of that given state.
Hi Mateusz,
I have great news to share! We no longer see this issue where in the Media Library, if you replace an image used for its Normal state, it will delete and replace the image for its Disabled state when the initial state is set to Disabled. This is when using our latest version of Storyline 360 (Build 3.72.29699.0).
Please let us know if you're still noticing the issue, and we'll be happy to continue troubleshooting with you in a support case.
