<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Sep 21, 2010, at 9:04 PM, Siarhei Siamashka wrote:</div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><br></font>But now returning back to this issue. Ideally, PAD repeat would be a better<br>default instead of NONE. Just because NONE repeat is a bit strange and<br>hard to accelerate in hardware. This is one example from freedesktop.org<br>bugzilla (and there are more similar reports):<br><a href="https://bugs.freedesktop.org/show_bug.cgi?id=27954">https://bugs.freedesktop.org/show_bug.cgi?id=27954</a><br></div></blockquote></div><div><br></div>Rather than PAD being the default, I think NONE should be changed to the equivalent of:<br><div><br></div><div> - intersecting the current clip with a quadrilateral that is equal to the bounds of the source surface transformed to the destination</div><div> - draw the image using PAD REPEAT</div><div> - restore the clip to as before.</div><div><br></div><div>The result is the black edges of the image are sharp antialiased lines no matter what the transform.</div><div><br></div><div>This is in fact what users expect, and also what other graphics libraries are doing (which explains why the hardware is supporting PAD directly).</div><div><br></div></body></html>