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
~flashrookie
--
er...
flexrookie (flash masta!) ; )
ok, new code, this time with IDs on dataProvider items for tracking.
yes, i know there's no direct renderer-to-provider relationship. i now
realize that the extra renderer instance is created for measurment
(according to alex harui). but i'm still looking for an explanation on
the multiple set
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 amyblankens...@... wrote:
--- In flexcoders@yahoogroups.com,
not an answer to my question, but a follow up for new itemrenderer
coders. i just changed my implementation of the renderer from a canvas
to a UIComponent, following alex harui's performance recommendation.
here's the updated renderer code (big thanks to peter ent's renderer
post at
--- In flexcoders@yahoogroups.com, flexrookie flexroo...@... wrote:
not an answer to my question, but a follow up for new itemrenderer
coders. i just changed my implementation of the renderer from a canvas
to a UIComponent, following alex harui's performance recommendation.
Some suggestions:
--- In flexcoders@yahoogroups.com, flexrookie flexroo...@... wrote:
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
7 matches
Mail list logo
