<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - pdftoppm shows black line artifacts with aaVector enabled" href="https://bugs.freedesktop.org/show_bug.cgi?id=90570#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - pdftoppm shows black line artifacts with aaVector enabled" href="https://bugs.freedesktop.org/show_bug.cgi?id=90570">bug 90570</a> from <a class="email" href="mailto:williambader@hotmail.com" title="William Bader <williambader@hotmail.com>"> William Bader</a> <pre>Splash::gouraudTriangleShadedFill() in Splash.cc has a lot of tests to ensure the processing order and an uncharacteristically large number of assertions. Is it possible that the author of that procedure hit the bug in SplashGouraudPattern::getParameterizedColor() + convertGfxColor() but thought that the problem was in gouraudTriangleShadedFill() and discovered that forcing a left-to-right processing order worked? Are all of the swaps necessary for the algorithm, especially the swap of X limits with the comment "FIXME I'm sure there is a more efficient way to check this."?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>