Apologies I meant longest text. It definitely works with useVirtualLayout set to false, I have already tried that and it works just fine. And technically I don't have enough renderers at once that that would actually be fine. I just was trying to figure this out as more of a learning experience since general practice is to use virtual layouts.
Kyle McKnight Senior UI Engineer - Accesso 602.515.1444 (M) On Wed, Oct 26, 2016 at 2:56 PM, Alex Harui <[email protected]> wrote: > > > On 10/26/16, 4:33 AM, "kamcknig" <[email protected]> wrote: > > >Test project attached. If you just click each of the buttons multiple > >times, > >as in "set 1" two or three times, then set 2 two or three times, you'll > >see > >it keeps resetting the width. The width should auto fit to the shortest > >text > >each time. > > Shortest text? What happens to longer text? I don't think I saw any code > trying to measure and find the shortest. > > How many rate renderers do you think you will need? In your test case, > the TileLayout has useVirtualLayout=true. TileLayout does some caching > when useVirtualLayout=true and I think that's screwing up the app because > the TileLayout is remembering information from the last layout pass and > using that in the calculation of the next layout pass. > > I set useVirtualLayout="false" on the List containing the TileList and > things seemed to be more stable. > > -Alex > >
