When creating an item renderer with any significant complexity, it is
usually a mistake to start with a containier.

 

I advise that you start over and extend or copy TreeItemRenderer.as

 

Tracy Spratt 
Lariat Services 

Flex development bandwidth available 

________________________________

From: [email protected] [mailto:[email protected]] On
Behalf Of Boson Au
Sent: Monday, February 09, 2009 11:48 AM
To: [email protected]
Subject: [flexcoders] Tree with Custom itemRenderer "Blocking"
dropIndicator...

 

Hi everyone, I'm not sure how I managed to get to this but here goes

basically here's the problem.

I have a tree that's been extended with a custom itemrenderer. I
actually set the default icon and label to be effectively invisible
and placed an itemrenderer (a hbox with other elements in it) over it. 

I've also added code to the tree such that when you drag a node over a
tree, it will open the tree after 1/2 second (aka spring loaded
folders). This way the user can just rearrange stuff to his/her
hearts content. 

I'm trying to mess around with the showdropfeedback and dropindicator
skin settings. I understand the theory behind it but I am finding a
weird error...

say when I grab a node and mouseover a branch, it'll open the branch
and list its children. The drop indicator works fine until the branch
opens and as I'm scrolling down the open children, the indicator
sometimes disappears... after some investigation, it seems like the
children are being created ON TOP of the indicator, which of course
makes it disappear. If I put a opaque background on the itemrenderer,
it'll definitely make the drop indicator disappear (since it'll be
behind the renderer)

is there a way to FORCE the indicator to be rendered on TOP of
everything? I want to provide user feedback on where the item will
drop... I thought about overriding showDrop feedback and creating a
BRAND NEW hbox or label or something and having the application add
that to its childlist, passing it the coordinates so it'll be placed
on top of the tree... but I'd love an easier solution...



Reply via email to