Not sure. Tree should be much better in
Flex 2. Sorry!
From:
flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Johannes Nel
Sent: Wednesday, January 18, 2006
1:07 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] modelChanged
event and mx:Tree
Hi
That whole "write your own damn tree component" trick?
Snark ;)
Alias
On 1/18/06, Johannes Nel <[EMAIL PROTECTED]> wrote:
> Hi All
>
> I have a model which dispatches the model change event which in turn gets
> caught by the mx:Tree (i have established this by subclassing the tree and
> checki
Timing is probably your problem. But anyway there's another solution to
accomblish your task you might want to consider. If products is your
dataProvider Array then you can bind to it via
and handle it via getter / setter properties
public function get productsChanged() : Array
{
ret
I think it stems from the use of an array in databinding. One way to
fix this is to reassign your dataprovider. Also you could broadcast a
model change event upon completion of the changes. This would hopefully
then trigger the sum to change.
I had a similar issue a while back and Tracy helped
4 matches
Mail list logo
