thedivclass Posted February 2, 2024 Posted February 2, 2024 Any multiple fills/strokes added to a layer will be removed when using captured states - undo and history can't correct this! I have also run into this issue using queries, but I am finding it more troublesome to reliably repeat. AD 2.4 (2240) • macOS 14.2 Thanks Bit Disappointed, debraspicher and Westerwälder 2 1 Quote
Bit Disappointed Posted February 3, 2024 Posted February 3, 2024 That sounds like a critical issue! Good catch! Westerwälder and thedivclass 1 1 Quote I simply no longer believe that there are any professional graphic designers here. Everything follows suit. Just everything.
Bit Disappointed Posted February 3, 2024 Posted February 3, 2024 16 hours ago, thedivclass said: Any multiple fills/strokes added to a layer will be removed when using captured states - undo and history can't correct this! I have also run into this issue using queries, but I am finding it more troublesome to reliably repeat. AD 2.4 (2240) • macOS 14.2 Thanks I easily recreated this one time but not a second time: Created two shapes Added fill and stroke on one Added one additional fill and one additional stroke from the appearance panel, a bit thinner than the first Moved it to the top in the appearance panel so both could be seen Captured a state Result: Multiple strokes gone Object was corrupted somehow, couldn't add multiple strokes to the particular object again, but could to other objects Want to add something, @Westerwälder ? Quote I simply no longer believe that there are any professional graphic designers here. Everything follows suit. Just everything.
Bit Disappointed Posted February 3, 2024 Posted February 3, 2024 Ah, easy to recreate: thedivclass 1 Quote I simply no longer believe that there are any professional graphic designers here. Everything follows suit. Just everything.
debraspicher Posted February 4, 2024 Posted February 4, 2024 How are Layer attributes being directly impacted by a Layer being hidden/unhidden? That's so error-prone. Bit Disappointed 1 Quote
Bit Disappointed Posted February 4, 2024 Posted February 4, 2024 49 minutes ago, debraspicher said: How are Layer attributes being directly impacted by a Layer being hidden/unhidden? That's so error-prone. I don't know, but I know that Serif wanted more frequent, smaller releases to avoid regressions. However, this just goes to show that good architecture requires foresight. I believe these layer states were rushed out in beta too quickly; the purpose of a beta isn't for customers to find and report fundamental flaws in the UI and architecture. However, I could be wrong, and it might be a minor slip-up; I'm just not that convinced. Quote I simply no longer believe that there are any professional graphic designers here. Everything follows suit. Just everything.
Staff Sean P Posted February 5, 2024 Staff Posted February 5, 2024 Thanks thedivclass, I've reproduced this and will get it passed on to development. thedivclass 1 Quote
Staff Affinity Info Bot Posted February 5, 2024 Staff Posted February 5, 2024 An issue raised in this thread ("Multi-stroke removed if layer state created and applied.") has now been reported to the developers by the testing team (Ref: AF-1946). Thank you very much for reporting this issue to us. Quote
thedivclass Posted April 10, 2024 Author Posted April 10, 2024 When this bug is resolved, I would love to see states work with multiple fills/strokes, rather than just not removing any additional fills/strokes. I frequently test styling & colour combinations by toggling visibility between multiple fills/strokes and being able to do this en masse via the states panel would be incredibly useful. (Presently, because of this bug, I fear using states at all though). Quote
Bit Disappointed Posted April 10, 2024 Posted April 10, 2024 It's really a terrible bug to have in a release version for so long. Bugs that so recklessly remove data from documents should be fixed asap, and as someone else says, it's not reassuring or confidence-inspiring that it can happen at all. Then the architecture behind is seriously shaky and insecure. chessboard 1 Quote I simply no longer believe that there are any professional graphic designers here. Everything follows suit. Just everything.
chessboard Posted April 17, 2024 Posted April 17, 2024 Hoped for a solution in 2.4.2, but this bug still exists. This makes layer states obsolet for my current project, though I could really benefit from it. thedivclass 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.