- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Mon, 31 Jan 2011 17:14:33 -0800
- To: Aryeh Gregor <Simetrical+w3c@gmail.com>
- Cc: Justin Anthony Knapp <justinkoavf@gmail.com>, public-html@w3.org
On Mon, Jan 31, 2011 at 4:45 PM, Aryeh Gregor <Simetrical+w3c@gmail.com> wrote: > On Mon, Jan 31, 2011 at 1:50 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: >> No. It's a fundamental restriction of an immediate-mode, >> one-shape-at-a-time API that this sort of thing will happen, >> especially if anti-aliasing is involved. > > The Flash version of the program looks like it's using an > immediate-mode, one-shape-at-a-time API: > > https://github.com/petewarden/stitchingbug/blob/master/FlashVersion/src/StitchingTest.mxml > > But it apparently doesn't exhibit the problem. Surely there's some > trick you could use to avoid the problem a lot of the time in > practice. Right; I corrected myself in my comment on the dude's actual website. >From what I know, Flash uses oversampling without AA to avoid jaggies. This is totatlly doable by browsers (that's the whole reason ImageData has its own width and height), but nobody's gone for high-resolution backing stores yet. ~TJ
Received on Tuesday, 1 February 2011 01:15:27 UTC