[flexcoders] Re: redundancy in custom ItemRenderer

2009-03-03 Thread flexrookie
> 2) I don't think you can make a variable bindable by putting [Bindable] > AFTER the variable (unless you were intending to make your button > variable bindable on dataChange). -- right, that was an error in my code. it should go before the getter, as in: = // Make the data property

[flexcoders] Re: updating an item renderer

2009-03-03 Thread flexrookie
--- In flexcoders@yahoogroups.com, "Amy" wrote: > > --- In flexcoders@yahoogroups.com, "flexrookie" wrote: > > > > hi amy, > > the manager class approach is interesting, and sounds safe from a > > memory-management perspective. thanks! > &g

[flexcoders] Re: redundancy in custom ItemRenderer

2009-03-02 Thread flexrookie
.height = unscaledHeight; } setActualSize(unscaledWidth, unscaledHeight); } } } === ~flexrookie --- In flexcoders@yahoogroups.com, "flexrookie" wrote: > > ok, new code, this time with IDs on dataProvider items for tracking. > ye

[flexcoders] Re: updating an item renderer

2009-03-02 Thread flexrookie
how would you guarantee that all itemrenderers safely unregister for the UPDATE event? ~flexrookie --- In flexcoders@yahoogroups.com, "Amy" wrote: > > --- In flexcoders@yahoogroups.com, "Tracy Spratt" wrote: > > > > The core concepts are that item renderers

[flexcoders] Re: redundancy in custom ItemRenderer

2009-03-02 Thread flexrookie
thanks amy, i found that info confirmed by alex harui's famous itemrenderer post, under recycling, here: http://blogs.adobe.com/aharui/2007/03/thinking_about_item_renderers_1.html ~flexrookie --- In flexcoders@yahoogroups.com, "Amy" wrote: > > --- In flexcoders@yahoogr

[flexcoders] Re: redundancy in custom ItemRenderer

2009-03-02 Thread flexrookie
A CALLED for ID: 1 StockInfoRenderer COMMIT PROPERTIES CALLED for ID: 1 StockInfoRenderer SET DATA CALLED for ID: 1 StockInfoRenderer COMMIT PROPERTIES CALLED for ID: 1 StockInfoRenderer CONSTRUCTOR CALLED. StockInfoRenderer SET DATA CALLED for ID: 1 StockInfoRenderer CREATE CHILDREN CALLED.

[flexcoders] Re: redundancy in custom ItemRenderer

2009-03-02 Thread flexrookie
> ~flashrookie -- er... flexrookie (flash masta!) ; )

[flexcoders] updating an item renderer

2009-03-01 Thread flexrookie
jects. the above two lines presuppose that i'm going to hunt for the item index every time a stock price changes. : ( another general question, do i even need the itemUpdate() call, or is that part automated? thanks for any advice! flexrookie

[flexcoders] redundancy in custom ItemRenderer

2009-03-01 Thread flexrookie
another question about ItemRenderers, using my previous stock example. i have noticed that my custom item renderer seems to be performing redundant executions. for a single dataProvider item, i see two renderer instances created. and for each instance, set data and commitProperties() are called re