Search the Community
Showing results for tags 'afd-2567'.
I wasn't gonna bother with this beta as it just seems to be under the hood maintenance stuff, although the new document setup is brilliant, I was kind of hoping there might be some un- mentioned tweaks to the "scale with object" for the stroke and FX tick boxes just so you could set them to be ticked by default (itsy bitsy niggles that catch me out every time) + also a way to have "assign" be the default when choosing colour profile - Still can't view bleed on artboards - I'm guessing these things are far more complex to implement than they appear. The feature that made me click the download link was "create palette from document" now you can create a CMYK document palette YAY! - tried it on a solid CMYK colour bar and it looks like it creates an RGB palette then converts it to CMYK which isn't useful as eg. solid Cyan C100 M0 Y0 K0 reproduces C100 M29 Y0 K12 - Also thought I'd try to create a document palette based on the colour bar as global (wish there was a way to set a global application palette) which I had to re-assign twice to the colours from the colour bar for them to link properly, even though they looked as if they where linking correctly the first time around, double clicking on the global swatch in the palette and changing the colour was having no effect on the linked colour, seemed that the work around was to select the colour on the page say solid cyan then link it to the magenta global swatch then back to the cyan global swatch for a porper link aaaaggghhhh! Other than that I did notice the vector brush tool was a bit more responsive, especially when trying to draw a continuous squiggle, it took quite a bit longer before it slowed to a crawl.
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.