This below code returns the wrong index for a tree using e4x xml data
as a provider wrapped into a xmlcollection.
I've been fighting with tree drag and drop off and on for a bit now,
can someone please confirm this is a bug or am I just doing things
wrong. I've posted about this before but it went unanswered.
I've looked at the tree code and it has not yet been scrubbed which
would lead me to think that it's not yet complete.
I simply need the item at the droplocation.
var currTree:Tree = Tree(event.currentTarget);
var rowindex:* = currTree.calculateDropIndex(event);
//get the current node that we are over
var currNodeOver:Object
if (currTree.indexToItemRenderer(rowindex) !=null){
currNodeOver = currTree.indexToItemRenderer(rowindex).data;
}
else{
currNodeOver=null;
}
The index I get back seems to correspond to the drop indicator,
however the drop indicator is not positioned properly, "Yet"; The
tree drops in the right location(go figure).
Anyway please either confirm this in one way or the other.
Thanks
Jason
------------------------ Yahoo! Groups Sponsor --------------------~-->
Get to your groups with one click. Know instantly when new email arrives
http://us.click.yahoo.com/.7bhrC/MGxNAA/yQLSAA/nhFolB/TM
--------------------------------------------------------------------~->
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
