Hi
long time Coreldraw user, slightly dismayed by the 2019 release...
In previous versions I could use the effects/transform/invert colour option on a vector object to quickly generate required objects. Now when I use this option in 2019, the object gets transformed and the edges are blurred as though it is converted to a bitmap. After this I can no longer change its colour etc. the final outputs are blurred too. I need to retain the vector objects
how do I get it to work as older versions?
CJ
Can you share an example file with vector objects in it that are showing this behavior when you "invert colors"?
For me, with simple vector shapes, applying that is simply changing the colors; it's not being applied as a "bitmap effect".
HI
thanks for the reply.
I tried several times to attached a file, and although it said it had uploaded it kept giving me errors trying to post it. I shared a copy from dropbox here:
https://www.dropbox.com/s/9914mjrllmd0kpl/test%20invert.cdr?dl=0
left is vector, right is the blurred version which is inverted
thanks
Thank you.
It appears to me that "invert colors" works in the "old way" when applied to shapes individually.
If they are a group, then it is applied as one of the new "non-destructive effects", which are bitmap effects.
The effect is significantly different, too, with respect to the colors it produces.
thanks. Is there any way to force it to revert to the old way?
once the non destructive efffect is applied, how do you 'flatten' it? using the effect/flatten appears to keep it as a bitmap and unusable!
cadjockey said:thanks. Is there any way to force it to revert to the old way?
I don't know of a way to make this work the same in 2019 as it does in previous versions. If it's something I had to do very often, then I might consider trying to write a macro to "individually" invert colors on the shapes.
I think that the best you can do is to understand that it works differently in 2019, and then use different workflows as necessary to "work around" that change in behavior. Others in this thread have suggested some different workarounds.