Colour Swatch Values in the Swatches Panel Not Restored After Double Clicking the Swatch Following a CMYK > RGB > CMYK Conversion

[Hangman]

In the current Beta v2.1.0 (1781) and v2.0.4 colour swatch values in the swatches panel are not restored after double clicking the swatch following a CMYK > RGB > CMYK conversion unlike in v1.X where the values are restored.

This results in the swatch colour values having to be manually reset and also runs the risk of the user unknowingly applying a colour swatch which now has incorrect colour values, more so when the colour palette is added as an application palette because the values for the swatch are not reset on closing the app which means the user has no way of knowing the colour values for the swatch are incorrect when opening a new document which clearly has potentially serious implications where brand colours are involved.

This applies across all three apps and also has implications where an application colour palette is linked between apps, i.e., after what can be an inadvertent RGB > CMYK conversion in one app because the default colour sliders in the swatches panel happen to be set to RGB, the swatch colour is changed to incorrect values across all apps so even working on a new document in a different app and applying the same swatch will now result in incorrect values being applied and the user really has no way of knowing unless they happen to recall the correct colour values for the swatch.

Note: The conversion to incorrect colour values only happens once on the first CMYK > RGB > CMYK conversion, after that the colour values remain fixed regardless of how often a CMYK > RGB > CMYK conversion is made directly in the swatches panel.

It would perhaps make sense if the swatches panel also included a lock colourspace option to match the colour palette as this would prevent this conversion from happening in the first place, although this is clearly a bug in itself that needs to be fixed.

[Sean P]

Hi Hangman,

I believe this is a macOS only issue as its not affecting Windows. I think what's happening is that changing the colour space is causing the actual swatch to get saved. Normally this should only happen if you manually adjust the value.

Easiest way to see this is by simply double clicking a colour swatch, changing the dropdown to be Greyscale and then clicking out of it - the swatch has been updated when it shouldn't.

I'll get this logged.

Thanks for letting us know! 

[Hangman]

Hi Sean,

16 minutes ago, Sean P said:

Easiest way to see this is by simply double clicking a colour swatch, changing the dropdown to be Greyscale and then clicking out of it - the swatch has been updated when it shouldn't.

That is exactly what is happening, in v1 after changing the dropdown to a different colour model, RGB or Greyscale and then back to CMYK, while you do see a colour change to now incorrect CMYK values (which IMO you shouldn't), double clicking the swatch resets the swatch back to its original CMYK values but in v2, as you say, the incorrect values are now being saved as the swatch values which means they are now incorrect which impacts linked swatches in the other apps.

As mentioned, this only happens one time on the first colour format change in v2.

Two questions

1. Would adding a Lock Colourspace padlock to the Swatches dropdown potentially prevent the colour conversions we are incorrectly seeing?
    
2. Does the .csv file used to generate the colour values only contain a single colour model, e.g., CMYK or does it contain multiple colour models e.g., CMYK, RGB, HEX, LAB and HSL, the logic being that if the latter, changing colour models should then reference the respective colour values for each and return the swatch back to the colour values for the respective colour model when changing between different colour modes.
    

[Sean P]

14 minutes ago, Hangman said:

Two questions

1. Would adding a Lock Colourspace padlock to the Swatches dropdown potentially prevent the colour conversions we are incorrectly seeing?
    
2. Does the .csv file used to generate the colour values only contain a single colour model, e.g., CMYK or does it contain multiple colour models e.g., CMYK, RGB, HEX, LAB and HSL, the logic being that if the latter, changing colour models should then reference the respective colour values for each and return the swatch back to the colour values for the respective colour model when changing between different colour modes.
    

I've now got this logged with development!

1. This behaviour is only happening on macOS. Both iPad and Windows are fine - so it shouldn't be saving when you just change the colour model as far as I'm aware.

2. The values aren't actually stored in a CSV, but inside a propriety propcol. I did log an improvement a while back that it would be nice to feedback to the user what Colour Space the swatch has been saved in, which should help a lot I think. Especially now the Swatches Panel displays the swatches based on the document's colour model.

[Hangman]

On 5/4/2023 at 11:41 AM, Sean P said:

Especially now the Swatches Panel displays the swatches based on the document's colour model.

Hi @Sean P,

I'm not sure I follow, could you elaborate... I don't think I'm seeing any change of behaviour in v2 but could equally be missing the obvious...