Joachim_L Posted February 7, 2020 Posted February 7, 2020 1. Create a colour in a palette and do not make it Global. 2. Create an element and assign the colour to this element. 3. Deselect the element, select it again and you see that the colour is highlighted (active / assigned) in the palette. 4. Turn the colour into a Global Colour and change the colour values. Result: The already correctly colour assigned element does not reflect the changes in colour values. So does this really mean I have to re-assign the colour? Quote ------ Windows 10 | i5-8500 CPU | Intel UHD 630 Graphics | 32 GB RAM | Latest Retail and Beta versions of complete Affinity range installed
Staff Callum Posted February 7, 2020 Staff Posted February 7, 2020 Hi Joachim_L, This behaviour is by design I'm afraid. I would recommend making a post in the Feature Requests section regarding this. Thanks C Joachim_L 1 Quote Please tag me using @ in your reply so I can be sure to respond ASAP.
Joachim_L Posted February 7, 2020 Author Posted February 7, 2020 Made a request right now. I can't believe this is by design. What was the intention behind this design decision? To work a bit longer? To provoke frustration? But Serif is smart, the intention was teaching / educating to think and plan before doing something. lacerto and MikeW 2 Quote ------ Windows 10 | i5-8500 CPU | Intel UHD 630 Graphics | 32 GB RAM | Latest Retail and Beta versions of complete Affinity range installed
MikeW Posted February 7, 2020 Posted February 7, 2020 I've written at most opportunities (for years) how swatches work in Affinity applications needs a total overhaul. Fixx 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.