I would set breakpoints in LayoutManager doPhasedInstantiation. If the layoutmanager never finishes validating, then you know that resizing the component has caused an invalidation loop where the component or something else is constantly being invalidated and re-validated.
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Tim Hoff Sent: Thursday, June 05, 2008 12:19 PM To: [email protected] Subject: [flexcoders] Re: Resizing component , browser freezes - how to overcome it Reinforces the value of getting the source. No way to know for sure man, sorry. -TH --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "alex" <[EMAIL PROTECTED]> wrote: > > Thanks Tim ! > > The problem is that it is a custom component (a map ) that I can only > use and not modify it..... > > --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "Tim Hoff" TimHoff@ wrote: > > > > > > Hi Alex, > > > > You might try making the code less intensive first; else you'll always > > have to find a work-around. If you're doing anything, especially > > calculations, on the render or resize events, you're probably spiking > > the CPU on a manual browser resize. I'm not hearing that cacheAsBitmap > > will work for you here, but you can give that a try as well. If those > > don't help, you can listen for the browser's RESIZE event and disable > > the offending code. Probably better to find a more direct solution > > though. > > > > -TH > > > > --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "alex" <myth_drannon@> wrote: > > > > > > I have Flex project which contains several different components > > > when I resize the browser windows, one of the components which is > > > calculations intensive causes the browser to freeze foraround 2 > > seconds. > > > Is there away to display the rest of components and delay the slow > > > component ( and may just display it's scaled Bitmap image), and then > > > run the component so it won't stuck the whole application ? > > > > > >
