Jump to content

Recommended Posts

If you right-click a swatch and make a copy, then rename the copy, you have two swatches of the same color. AFPUB does not respect their name differences. When you apply the second swatch to an object, and then come back to that object later, it will have reverted to the original swatch and name since the two swatches have the same HSL - the swatch becomes highlighted when you select an object - the wrong swatch.

This is a bit problematic if you wish to, say, assign #one swatch to section one of the document and assign #two swatch to section two of the document. The idea would be to come back later and change the colors of section two via editing the second swatch (the copy). It seems that you have to make a slight HSL change so that the objects don't confuse AFPUB by having the same HSL values.

Essentially, this means you have to create a new colour swatch for section two that is not a complete duplicate of swatch #1.

Screen recording: two picture objects, a single color swatch is used on each. Copy that swatch to make a duplicate. Assign duplicate swatch to second item. Select first object - uses original swatch. Select second object - original swatch is highlighted. Swatch copy is ignored and not used since it is entirely a duplicate.

I would prefer to have an object keep the same swatch that was assigned and not revert to another with the same settings.

 

Share this post


Link to post
Share on other sites

> AFPUB does not respect their name differences.

In your video you do not rename the swatch copy, did you? Therefore the app gets confused by its auto-naming with twice an identical name. The global swatch copy naming issue appears to be reported here, too:

 


macOS 10.14.6, Macbook Pro Retina 15" + Eizo 24", Affinity in Separated Mode (documents merged)

Share this post


Link to post
Share on other sites

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.

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.


Patrick Connor
Serif Europe Ltd

Latest releases on each platform 

 

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.