Re: [flexcomponents] Re: Extending Tree :: Using itemRenderer, kills tween

Wed, 23 Aug 2006 12:59:45 -0700

Hey deepa,

Yeah, I figured as much, I have studied the Tree and List and ListBase for awhile.

The only thing I can think of was I was calling expandTree(), I think that was what was triggering the update.

My logic last week was fouled, I rewrote some things and it is working to my specs for now.

When you set something in a dataDescriptor that shouldn't call updateDisplayList() right? I don't see anything that call any collection event.

I love the Tree though, there is a lot that can be done with extending it.

Peace, Mike

PS, I found a bug in it that is not a good one. I am looking into a work around right now.

If you expand a tree iten and the tween is ahppening, if you scroll or use the mouse wheel at the same time it is tweeing, there are a bunch of whitespace rows that show up and it messes up the whole tree.

The only way to remedy is to restart the app, which is not good. ;-)

On 8/23/06, Deepa Subramaniam <[EMAIL PROTECTED] > wrote:

Hi Michael –

 

Glad you found a workaround. An addition to your tween ending list is that anything that causes an updateDisplayList() call to be invoked mid-tween will end the tween. You can see the logic in Tree.updateDisplayList().

 

-deepa

 

From: [email protected] [mailto:flexcompone [EMAIL PROTECTED]] On Behalf Of Michael Schmalle
Sent: Thursday, August 17, 2006 4:09 PM
To: [email protected]
Subject: [flexcomponents] Re: Extending Tree :: Using itemRenderer, kills tween

 

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 <[EMAIL PROTECTED]> 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.




--
What goes up, does come down. __._,_.___


SPONSORED LINKS
Software development tool Application development software Development software
Development outsourcing software Embedded software development

YAHOO! GROUPS LINKS



__,_._,___

Reply via email to