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?
Just a side note, this happens in other vector apps. Everyone I've tried. It is sometimes called a conflation artifact. The solutions in all are either matching the stroke to the object color, putting a copy or two behind it, or ignore it on screen and disable anti-aliasing on export to bitmap or otherwise change the export render method. As such I don't know if it can be called a bug. It is just how anti-aliasing works. No great mathematician has come up with a better way.
This is when objects are abut, not when there is actual area between objects.
Some esoteric rendering reading:
http://w3.impa.br/~diego/projects/GanEtAl14/sample.html?tiger
computergraphics.stackexchange.com/.../what-is-illustrators-vector-rasterization-process
Thanks for your comments on this, David - and for the links, too!
From some of Hendrik Wagenaar's comments, I get the impression that they could fix this, and that they know how to fix this - but have chosen not to. To quote Hendrik from that thread:
Yes, it's a bug, but a very difficult bug to fix (Easy if you aren't concerned with render speed or memory usage, just render 8x8 supersample).
That was posted almost 7-1/2 years ago. I don't know if it is still considered to be "too expensive" in terms of computer resources.
(It might be wrong for me to use the word, "fix". As discussed and demonstrated at the links you posted, it's not necessarily a simple right/wrong thing for all situations.)
David Bevins said:disable anti-aliasing on export to bitmap or otherwise change the export render method
See my Quick Export macro, which can use CorelDRAW's "supersampling" option for anti-aliasing when exporting to bitmap (not applicable when exporting a transparent PNG).
We are not talking about exporting to a Bitmap again (it's Vectorized from Bitmap). But it's the trace result, which have the problem. And what you mention, is things which already has been proved, and in reality don't change anything to the problem.Read the whole thread, for some of the proposed solutions, and why they do not fix the real problem!