I'm not sure if it applies in this case, but TileList definitely has some bugs in its measuring and layout code (or at least did in Flex 2 -- not sure if they fixed it). In particular, when calculating its preferred width it basically does (itemRenderer.width + horizontalGap) * numColumns. That's one extra horizontalGap in there... possible the extra space you're seeing on the end?
In several pixel-perfect layouts I've had to actually *not* use TileList because of the bug... though at the time I wasn't aware of the technique of monkey-patching (where if you create a class in the project that matches a class in the SDK the project class overwrites it), which would eliminate the need to modify the SDK source (which I generally avoid). Troy. On Fri, Jun 13, 2008 at 7:31 AM, Amy <[EMAIL PROTECTED]> wrote: > --- In [email protected], "Alex Harui" <[EMAIL PROTECTED]> wrote: >> >> MXML is not HTML. I don't remember seeing a specification of >> columnCount or width of the TileList in pixels. You could be seeing >> round-off error or simply that the computed width of the tile doesn't >> fully cover the TL. > > The columncount is 7. Would tweaking the size of the itemrenderer help? > >
