![]() It's because the renderer only sees one patch at a time. It's not, strictly speaking, because the edges of the polygons are not matching. This is a fairly difficult to solve problem in general. ![]() The problem with alpha <1 occurs when stroking the outline causes overlaps they then show up as dark boundaries. I'm not sure what would be the proper way to implement it, though-by changing the behavior of stroke with zero linewidth inside the backend, or by setting the default linewidth. If it turns out to commonly work for pdf, and to do no major damage in the cases where it doesn't help, then I would be happy to make it standard. In a quick test just now, it appears to work for pdf and eps using evince or firefox as the viewer, but not for svg on firefox. On those previous occasions I have found using a tiny linewidth to not work uniformly. I think the most recent conversation was in connection with hexbin someone who is good at github searching might want to find this, and possibly other issues where it has been discussed. ![]() This whole problem keeps coming up, every year or two, and more than once I have conducted tests to see if I could find a general solution. ![]() Yes, we decided long ago that we wanted zero-linewidth to mean "don't stroke", instead of the postscript meaning of "stroke with the minimum linewidth (presumably one dot)". ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |