Someone here on the forum has already realized that when the shading is grouped when it grows it distorts the pixels, if it is not grouped it looks good. I know that this error is happening in Corel 2020 and 2019, in other versions I don't know.The new internal shadow effect of Corel 2020 even grouped does not happen this error when making it bigger.Does anyone know any solution to this problem?I made a sample video
This is another one of Corels pesky ass refresh bugs, makes the program a PITA to use. You'll find them in lots of places like the edit bitmap feature, immediately after you import an image you need to save the file to use all features also the object docker. So if you see weird try saving or saving , closing and reopening orvw refresh of some type.
David Milisock said:immediately after you import an image you need to save the file to use all features also the object docker.
That one is new to me. Can you elaborate, please?
This issue exists in any work flow that has the user importing images into Draw that have a different color space then the active Draw document in which the image is being imported, specifically if the PP application default color space does not match your Draw document.
I like most professional image editors utilize an archival approach for images, correcting in RAW, then saving to a server as a wide gamut RGB color space like prophoto to maintain image integrity. Also allowing the image to be utilized in various smaller color spaces in future Draw documents.
In most cases Photo-Paints default application color management does not match your current Draw document, especially if you create documents for varied output devices and or global regions.
Specifically the user who uses the edit bitmap feature sending the image to Photo-PAINT for editing sees this issue or suffers without knowing. Quite frankly, who wouldn't use that feature?
EXAMPLE: Draw document utilizes Adobe RGB 1998 and GRACOL CMYK, an image with a mismatched color space is imported into Draw, Photo-Paints color management is set for professional photography, IE wide gamut RGB and project specific regional CMYK.
The experienced choice is for the user to have Draws color management set to warn of the profile mismatch, (this is done in case one mistakenly imports an image that had not be pre corrected in it's resident colorspace, you can stop the process and correct the images for archival) then to select convert to document color space for RGB images and assign document color space for CMYK.
Once the image is imported into Draw the user must immediately save the document to link the document color space with the newly imported image, or images if you imported more than one.
High quality image corrections must be done in Photo-PAINT and if if this saving process is not done as described, upon opening the image in Photo-PAINT the images color space will be one of Photo-Paints application default color spaces rather then the active Draw document from which it came and in fact the image may function in an uncolor managed manner. Therefore edits will be incorrect when the edited image is returned to Draw
This is why we use the edit bitmap feature for high quality edits only in Photo-PAINT and what it does, call it a bug or a peculiarity but it's one of the many PITA issues with CorelDRAW.
The real issue for Corel is to recognize the huge number of these simple *** issues and FIX them, screen refresh, objectvdocker not updating, shadows not updating, the list goes on forEVER!