Jump to content
fde101

Global color bug still present in 1.8 beta

Recommended Posts

Sadly, the global color bug is still present in the 1.8 beta.  Easy to reproduce:

  1. In a new document, create a rectangle and make it black (0% red, 0% green, 0% blue - or equivalent in any color system).
  2. Create a global color from that black, leave it named as "Global Color 1", set the swatches palette to view in list mode, and select the global color.
  3. Create a second rectangle.  Make it the same black.
  4. Create a new global color from that same black, leave it named as "Global Color 2", select that color from the swatches palette.
  5. Select either rectangle by clicking on it.  "Global Color 1" is selected in the palette regardless of which rectangle you click on, even though one of them is assigned to "Global Color 2".

 

This is a problem, because it suggests that both rectangles would be changed if you updated "Global Color 1", but only one of them will be.  The interface is not accurately reflecting the reality of the objects in the document.

Share this post


Link to post
Share on other sites
24 minutes ago, fde101 said:

Sadly, the global color bug is still present in the 1.8 beta.

Unless the release notes said it was fixed, we should assume that it wasn't.


-- Walt

Windows 10 Home, version 1909 (183623.476), 16GB memory, Intel Core i7-6700K @ 4.00Gz, GeForce GTX 970
Affinity Photo 1.7.3.481 and 1.8.0.514 Beta   / Affinity Designer 1.7.3.481 and 1.8.0.514 Beta  / Affinity Publisher 1.7.3.481 and 1.8.0.518 Beta

Share this post


Link to post
Share on other sites

Two more related issues are in the behavior when a swatch gets copied and edited: Then ...

• the copy gets the same, identical name
• an edit of the selected copy does not edit the copy but the previous swatch.

1656575882_swatchcopyedit1.jpg.c14e9599946031a9a1f8859fc31a54a6.jpg

745355002_swatchcopyedit2.jpg.9cfe82ffe8a033f84a98f70b75ef8264.jpg

791029311_swatchcopyedit3.jpg.cf228f928ec7bd787ee80c57247a1f22.jpg

1613804927_swatchcopyedit4.jpg.41d1f882a3ce72f245a9b478306e3e21.jpg

1402325164_swatchcopyedit5.jpg.75e4c1b7b7ec6881c1cf3d865eb477e8.jpg

It seems to be a general naming issue within the app UI at specific spots: Compare the identical custom names of copied master pages.
( – whereas a copy of a text style does not get an identical name but gets "1" auto-added)

 


macOS 10.12.6,  Macbook Pro 15" + Eizo 24"

Share this post


Link to post
Share on other sites
1 hour ago, thomaso said:

an edit of the selected copy does not edit the copy but the previous swatch.

Good catch - you can't rename the copy either, it complains that the name already exists, even though it is the OLD name that exists in duplicate and not the new name.

Share this post


Link to post
Share on other sites

These are both logged with us, but as Walt says if something isn't in the changelist it likely hasn't been fixed - I've updated these reports though


Serif Europe Ltd. - www.serif.com

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

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.