I just downloaded the Corel Grpahics Suite 2020, in a hope of, that the frustrating error with the white lines in Trace results from Bitmap was solved. But I can see, that this error is still existing. Why is this error still existing, after years as a known problem?
It is a pain that these white lines show in the display, although I've never had them show in any final output file.
However there is a workaround. You need to give each object in the scanned result the same colour outline (hairline width) as the fill. Sounds like too much hassle - there's a (free) macro for that: macromonster.com/.../
Thanks for the reply. But it will be a real pain, if I should give every single object an outline from the scan, the same color as the objects. I sometimes have both three and four thousands objects.And I know the macro, you advice. But with the macro, I have to run it every time, I do a scan. I really feel, that it's frustrating, that such an error, which has been in the Coreldraw Trace function, for years, are still not corrected.At the moment, I do an extra scan, with a very low resolution, and put behind the scan I have to use; and by this, the white lines "disappear" (covered by the under laying scan). But it just fill up extra objects.So come on Corel, and get that error fixed ;-)
RoyReed said:It is a pain that these white lines show in the display, although I've never had them show in any final output file.
I have read that it's an anti-aliasing thing. If the content is exported as a bitmap, using anti-aliasing, then the "white lines" problem can show up in the resulting bitmap.