woefi Posted February 14, 2019 Share Posted February 14, 2019 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. fde101 1 Main machine: iMac 2019 (21,5-inch 4k, 6core), 64GB RAM, 1TB nvme + 2TB ssd, running on Mac OS 13; Display setup: 28" 5k Display (primary) + 21,5" iMac4k-Display for studio panels (secondary); Keyboard layout: german apple extended keyboard (aluminium); Link to comment Share on other sites More sharing options...
Staff Sean P Posted February 26, 2019 Staff Share Posted February 26, 2019 Thanks for letting us know Woefi, I've passed this onto development. woefi 1 Link to comment Share on other sites More sharing options...
Recommended Posts