(Untitled)

[inferis]

Deeply unimpressed with the Flex Tree control - it seems incredibly buggy and prone to unintelligible exceptions (there's also some weird infinite looping going on). I really don't have time to write my own, so I'll probably have to think of a different way to represent the data. This is irksome.

UpdateIt seems that one of the bugs I had found was

Comments

[merlinc]

What sort of bugs are you getting? Have you used validateNow() to refresh the provider (otherwise it waits until the next render cycle)

[inferis]

Wow, that's not completely unobvious at all.

I'm not digging the flex documentation tbh, it's very, very light on Whys and Hows.

[merlinc]

I usually flip between:

Flex Documentation: http://livedocs.adobe.com/flex/3/html/
Language Reference: http://livedocs.adobe.com/flex/3/langref/
and occasionally I drill down to the source code c/o Flex Builder.

If they fail, I google or take a look at AXNA (feeds.adobe.com)

[inferis]

In answer to your actual question, they're mostly redraw bugs. I'm lazy loading some of the branches and if I don't reattach the dataProvider after each update, the tree not only doesn't refresh the scroll bar correctly, but if I'm expanding the last item in the list, it can lose the tree entirely.

I shouldn't have to deal with redraw issues on controls I haven't written myself. Maybe it's just me, but I think controls should be aware of their own data and be able to force a redraw/update whenever it changes - it's not like that's particularly difficult to do with the data binding framework in Flex.