The principle for the first strategy is that you would only have one big label with spaces where you float the icons, and you would only float the icons that are within the display area.
The same principle applies to the second strategy. It'll be hard to decipher from the list classes code (ListBase.as, TileBase.as), but we only create rows/cells/textfields for the things that are displayable. There's an upper limit on the addressable pixel space so you can't just keep adding things beyond either 2880 pixels so we typically virtualize things. Your control really sounds like a List with a custom renderer for each conversation where that renderer can have icons scattered through it. -Alex ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of superstella_uk Sent: Friday, January 26, 2007 8:32 PM To: [email protected] Subject: [flexcomponents] Re: Drawing Text, can it really be so difficult? --- In [email protected] <mailto:flexcomponents%40yahoogroups.com> , "Alex Harui" <[EMAIL PROTECTED]> wrote: > > Haven't really thought this through, but you could insert enough spaces > in the text to make room for the images and float the visible images > over those spaces. I think there is enough APIs on TextField to be able > to pull that off. > Ill look into this, I suspect this method will improve performance, but will not solve the problem of many labels being revalidated > > > You might also making a custom scrolling container based on > ScrollControlBase that won't try to apply layout to all of its children > and just trust your mix of TextFields and Images. > Thanks, this is interesting, and probably my best chance of creating a workable solution. Do you have any advice on where to start with this? Ill start digging through the source tommorrow and see what hooks it gives me Thankyou
