Jump to content
woefi

creating colour palette from document gives wrong(ish) colours

Recommended Posts

So, since the first beta came out I keep testing and hoping that the colour palettes finally work "right". Now with release .238 (mac) this bug is still not fixed.

Obviously whats happening is, Designer scans all the colours using "RGB-view" and includes shadow effects and placed images,

which produces:

A) way too many color swatches (if you have an image placed or a text with simple shadow effect)

B) the wrong colour values if (it should be clear, we are talking about a dtp-app) the colours are mostly CMYK.

C) the colours are not global AND are not used by (or applied to) the objects (in which the function found it to begin with)

 

Especially in desktop publishing, you have to have a clean view over used assets, links, colour-swatches, fonts used in the document. Unlike in a photograph, you cannot use a "slightly brighter" red or a "subtle darker" grey in different places of your pages, just so that the overall "feeling" is the same. These must be, by default, "global colours" and you have to rely on the accuracy!

 

I understand there is "some" complexity as all three apps re-use the same engine. Most users probably don't need this behaviour in Photo and some more need it in Designer, but in Publisher it is essential to have consistent values across multiple related documents.


  • Production-System: iMac (21,5-inch, Late 2013), 16GB RAM, 2TB nvme-SSD, running on 10.14.4 Mojave;
  • Display Setup: 27" Thunderbolt Display primary + 21,5" iMac-Display secondary for palettes;
  • Keyboard-Layout: German apple extended keyboard (aluminum);

 

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

×