Hmm well probably becuase I hadn't thought of it. :)

Sounds a good idea, one singleton class providing the 
invalidate/revalidate service to all non-ui classes in the 
application that require it.

tks


--- In [email protected], "Michael Schmalle" 
<[EMAIL PROTECTED]> wrote:
>
> Hi,
> 
> Just a quick thought, is there any reason you wouldn't want to do 
what the
> layout manager does with it's composition of a UIComponent for 
callLater()
> that's in sinc with the frame render?
> 
> Or is this a non flex framework component?
> 
> Mike
> 
> On Tue, Sep 9, 2008 at 6:05 AM, reflexactions 
<[EMAIL PROTECTED]>wrote:
> 
> >   Wondering when a timer with a timeout or interval of 0 will run.
> >
> > Now, at the end of the current frame, at the start of the next 
frame?
> > If the latter is it before or after the LayoutManager runs?
> >
> > Just thinking about how to give a non-component class the 
equivalent of
> > invalidateProperties/commitProperties.
> >
> >  
> >
> 
> 
> 
> -- 
> Teoti Graphix, LLC
> http://www.teotigraphix.com
> 
> Teoti Graphix Blog
> http://www.blog.teotigraphix.com
> 
> You can find more by solving the problem then by 'asking the 
question'.
>


Reply via email to