Jump to content
You must now use your email address to sign in [click for more info] ×

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.

Link to comment
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
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
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.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1

Link to comment
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.

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

Terms of Use | 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.