Joachim_L Posted January 3, 2020 Posted January 3, 2020 Starting the new year with a clean new application palette was a brillant idea I had this morning. So I defined my colours, including some global colours, named the palette nicely and exported it for further use. Next step was importing the palette as an application palette, but doing so all global colours vanished. Next step was importing the palette as a document palette, doing so all global colours were preserved. Nice, but not what wanted first. Per definition a document palette is saved with the document. But there is also the option to set a document palette as default for a colour space. The default palette seems to act in some way like an application palette, but only for the specified colour space and without the fancy Affinity logo and that I always have to scroll up in the dropdown list of palettes. Is it intended that global colours are lost in the application palette or is it a bug? Quote ------ Windows 10 | i5-8500 CPU | Intel UHD 630 Graphics | 32 GB RAM | Latest Retail and Beta versions of complete Affinity range installed
R C-R Posted January 3, 2020 Posted January 3, 2020 7 hours ago, Joachim_L said: Is it intended that global colours are lost in the application palette or is it a bug? According to the online AP Global colors help topic what should happen is global colors are converted to standard colors: That is what happens on my Mac -- the global colors are not "lost," just converted to standard ones, & they retain any custom names I have given them as a document palette. So for you are they truly "lost" or just converted? Joachim_L 1 Quote All 3 1.10.8, & all 3 V2.5.7 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7 All 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7
Joachim_L Posted January 4, 2020 Author Posted January 4, 2020 Hmmm, less writing, more reading should be my future tasks. Overread this passage. The Globals are simply converted not lost. In my eyes not preserving the Globals is not a good idea. Quote ------ Windows 10 | i5-8500 CPU | Intel UHD 630 Graphics | 32 GB RAM | Latest Retail and Beta versions of complete Affinity range installed
R C-R Posted January 4, 2020 Posted January 4, 2020 1 hour ago, Joachim_L said: In my eyes not preserving the Globals is not a good idea. Just guessing but that might be because in Affinity global colors are considered to always be specific to a document, or at least to its color space? Quote All 3 1.10.8, & all 3 V2.5.7 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7 All 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7
Joachim_L Posted January 4, 2020 Author Posted January 4, 2020 Why this limitation? For me it would be helpful to have a consistent application palette with global colours across all three applications. But it is just my wish. Quote ------ Windows 10 | i5-8500 CPU | Intel UHD 630 Graphics | 32 GB RAM | Latest Retail and Beta versions of complete Affinity range installed
walt.farrell Posted January 4, 2020 Posted January 4, 2020 1 hour ago, Joachim_L said: For me it would be helpful to have a consistent application palette with global colours across all three applications. But consider how global colors operate. The real purpose of a global color is so that when you change the global color, all objects assigned that color also change. That can work with a Document palette and a single document, but how would it work across all your documents if the global color were changed in an application palette? Affinity could not search every file on your computer looking for objects that used that color and update them. In essence, "global" has meaning only within a single document, and thus only within a document palette. Alfred and R C-R 2 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, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
R C-R Posted January 4, 2020 Posted January 4, 2020 13 minutes ago, walt.farrell said: That can work with a Document palette and a single document, but how would it work across all your documents if the global color were changed in an application palette? Affinity could not search every file on your computer looking for objects that used that color and update them. Even if Affinity could somehow do this (which typically would require devoting large amounts of system level resources to that task that would leave little left for application level tasks until that process completed), imagine the problems that could cause with document portability if for example a document with one or more colors defined in some 'application-global' color palette was opened on another computer that did not have that particular 'application-global' color palette installed on it, perhaps from cloud-based storage. The only foolproof way I can think of to avoid that (& likely some other portability issues as well) is to make sure the color palette is embedded in the document & 'travels' with it -- IOW, that it is a document color palette. walt.farrell 1 Quote All 3 1.10.8, & all 3 V2.5.7 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7 All 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7
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.