Global swatch link retained for objects using earlier color definition of a modified global color

[lacerto]

I am not sure if this is a bug or intended design, but if the latter this is a potentially hazardous feature.

If you create a document palette and then define a global color swatch and make sure that you assign an object e.g. fill using that color swatch (so that you can see that there is a link with the object and the swatch), then modify the swatch's color definition (and see the object to change the color accordingly), then go on and select the object and assign it a fill from "Recent colors" (which shows both the changed and original color definitions of the same swatch), you see, as expected the object to have the fill color changed to that earlier color and also lose the link to the global color swatch as listed in the document palette. 

But now if you deselect all and change again the color definition of the global color swatch shown in the document palette, the color of the object (using the earlier instance of the swatch) changes to match the modified definition. That is, it still has the link to the original swatch even if it does not show this. The link can be broken only by selecting the object and manually redefning for it a new color value, removing the color definition, or by assigning a new global or local color swatch.

I wonder if this could be changed so that the recent color loses its connection to a subsequently changed global color swatch and becomes a global color of its own, or just a  mere color definition without any connections?

[Patrick Connor]

Sorry.

Thank you for reporting a problem using 1.7.x . It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script.

Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum.

• Report a Bug in Affinity Designer
• Report a Bug in Affinity Photo
• Report a Bug in Affinity Publisher

Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem.

This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the current 1.8.3 release build.