Ok,
Not to answer my own question but, for those that use this as an archive, I'm
better off not even asking.. I will eventually figure it out.
The problem was I was listening for a dataChange event in the item renderer. I
was trying to simulate a creationComplete event in the item renderer as a quasi
initialize queue for the renderer getting recycled.
Well, it didn't work right and it was somehow invalidating the tree to stomp
out the tree's tween.
The way I fixed it? Well, I reversed my logic and say that a client has to
specifically set toggleVisible in the CheckBoxTree in the dataProvider to start
off with.
This got rid of the listening for dataChange event and erased the call to
setToggled() I was making to the dataProvider.
I suspect that the dataProvider was getting a refresh event or something and
that was tripping up the Tree at the same time I was making the tween fire.
Anyway to busy to get too the actual root of it but, by far it doesn't seem to
be a bug in the Tree, just a weird insane timing issue.
Peace, Mike
On 8/17/06, Michael
Schmalle <teoti.graphix@gmail.com>
wrote:
Hi,
I have looked high an low through the Tree class for this answer and just don't
understand.
Anybody know the reasons why a Tree tween gets cut other than;
- isOpening == true
- duration 0
- row count stuff
- row length > 20
?
Could an invalidateSize() be invalidating something from the item renderer
that is killing the tween? I am using the standard xml dp from the examples(so
it is not large) no branch is larger than 3.
Once I take this line out of my class;
itemRenderer = new ClassFactory(CheckBoxItemRenderer);
The tree tween fine again.
No matter the internals of the extension in the tree, the disclosure icon won't
even open it. What I am saying is there is NO connection to any of the extended
capabilities of the tree to the disclosure icon.
Peace, Mike
--
What goes up, does come down.
--
What goes up, does come down.
