benedictchua Posted January 16, 2023 Posted January 16, 2023 (edited) Hi Affinity team, I received this prompt when renaming a fill in Affinity Designer. While I understand that the prompt indicates the change is permanent / non-reversible, it would be great if the language of the prompt could be simplified. A blurb like "This change is reversible" or "You can undo this later" would help improve usability. Or removing the subtext entirely - If I try to "undo" the change, have the application present a pop-up message. Thanks for looking through this suggestion! Edit: TY LondonSquirrel for the correction Edited January 16, 2023 by benedictchua Quote
benedictchua Posted January 16, 2023 Author Posted January 16, 2023 Sorry, yes, you're completely correct. I misread the subtext blurb. Will update to request "This change is reversible" or something easier to parse. Thank you! 🙂 Quote
RNKLN Posted January 16, 2023 Posted January 16, 2023 Why even bother to have a message at all? Quote Affinity Photo - Affinity Designer - Affinity Publisher | macOS Sequoia (15.3) on 16GB MBP14 2021 with 2.6.x versions
loukash Posted January 16, 2023 Posted January 16, 2023 37 minutes ago, RNKLN said: Why even bother to have a message at all? This. Since almost everything is undoable in Affinity, only those actions should even bother to warn when they are not. Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2
Fritz_H Posted January 16, 2023 Posted January 16, 2023 I don´t know if the following is language-specific but in german we say, that people do not read/understand/"process" a NOT in a message. Wording-Suggestion: "This operation can not be undone."(I know, still contains a "not" ...) but the real question is: WHY? Quote
walt.farrell Posted January 16, 2023 Posted January 16, 2023 43 minutes ago, loukash said: This. Since almost everything is undoable in Affinity, only those actions should even bother to warn when they are not. The message says you cannot undo the change. That's why there is a message warning you. (I'm finding this conversation confusing, and I'm not sure which participants understand that correctly.) Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
loukash Posted January 16, 2023 Posted January 16, 2023 1 minute ago, walt.farrell said: The message says you cannot undo the change. Haha, you're right. Even more proof that it's just bad UI communication. Fun fact: Renaming a swatch is an undoable operation on Mac (v1.10.6)… Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2
loukash Posted January 16, 2023 Posted January 16, 2023 5 minutes ago, walt.farrell said: (I'm finding this conversation confusing, and I'm not sure which participants understand that correctly.) English is only my 3rd language, so I thought I'd better look up the New Oxford Dictionary: Quote undoable |ʌnˈduːəb(ə)l| adjective informal unable to be done; impracticable: some wild request that's almost undoable | (as noun the undoable) : one man is daring to do the undoable. Hm… Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2
walt.farrell Posted January 16, 2023 Posted January 16, 2023 32 minutes ago, loukash said: Fun fact: Renaming a swatch is an undoable operation on Mac (v1.10.6)… Interesting fact. As it turns out, that's also true on Windows, but only if the swatch is in a Document Palette. If it's in an Application Palette, the rename operation is not recorded in the History, and you cannot Undo it. There's a bug, though, because you get the warning message in both cases (Document and Application), but it is undoable when it's in a Document Palette because in that case there is a History entry. Note: History records changes to the document, so it makes sense that changes to a Document palette are recorded, but changes to an Application Palette are not. But the message should only be issued for renames within an Application Palette. Note 2: Getting the message (for a swatch in an Application Palette) may be considered important because you lose information when you perform the rename. For example, you might have a swatch named H:0 S:100 L:50 and if you rename it to XYZ you've now lost the HSL values unless you go back and measure them. That's perhaps not terribly important for HSL-based colors, but recovering the value is more difficult than simply performing an Undo. loukash 1 Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
walt.farrell Posted January 16, 2023 Posted January 16, 2023 53 minutes ago, LondonSquirrel said: You can not unrename this palette. How about that for some word mangling? Just to start the mangling, please note that it's not about renaming a palette. It's about renaming a swatch within a palette. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
Dan C Posted February 23, 2023 Posted February 23, 2023 Hi @benedictchua & all others here, Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here. I can confirm that I've logged this with our developers - as I understand it this wording means you should not be able to undo the change, but as reported this it not always the case. Therefore I have requested that the wording is changed to be more clear, removed when editing document swatches (as it is not true) and to bring consistency to the wording in the History step itself when editing the name of a regular or registration swatch, compared to a global colour swatch. I hope this helps walt.farrell 1 Quote
Staff Affinity Info Bot Posted March 15, 2023 Staff Posted March 15, 2023 The issue "Inconsistent behavior when renaming and undoing renaming of swatches, warning shown in UI is not always applicable" (REF: PD-371) has been fixed by the developers in internal build "2.1.0.1728". This fix should soon be available as a customer beta and is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us. 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.