"Yes, we discovered this very soon after shipping that this data should
have been exposed. We have a bug for this already logged internally, so
we will work on fixing it for the future. For now, I think you will have
to rewrite your own updateDropData function, which is unfortunate."
So I'll have to stick with my original plan of duplicating a few methods (as stated in my original post).
On 8/21/06, thunderstumpgesatwork
<[EMAIL PROTECTED]> wrote:
I'm glad it's not just me! So, were you able to get something working
for your scenario?
Anyone from the Adobe team want to confirm this and/or offer
alternative solutions?
thanks,
Thunder
--- In flexcoders@yahoogroups.com, "Jason Y. Kwong" <[EMAIL PROTECTED]>
wrote:
>
> I've running into this myself right now as well. If you look at the
Tree
> code, you can see that the "drop parent" is being tracked in the
variable
> _dropData.parent. It gets calculated in the method updateDropData().
> Unfortunately, both the variable and the method are private, so they're
> useless as is (another example of Adobe being overly private, I'm
afraid).
> I've had to duplicate (and tweak) the updateDropData() method to
make use of
> the algorithm. The methods getChildIndexInParent() and
getChildren() had to
> be duplicated as well.
>> On 8/18/06, thunderstumpgesatwork <[EMAIL PROTECTED]> wrote:
> >
> >
> > Bump... I'm trying to do similar. Though I need to do it in the
> > DragOver event, and determine under which node it is going to be
> > dropped. I need to do this because certain places in the tree are
> > acceptable places to drop certain items...
> >
> > I know I can get the "dropIndex" by using the tree function
> > "calculateDropIndex" however this is not enough. It simply tells me
> > where in the list of displayed nodes it will go. So if the item is
> > being placed between the last item in a lower level node and the
> > continuation of the next level up, the index is the same, but the
> > parent of the ending drop is different.
> >
> > I can tell the Tree internals are tracking this because the drop
> > indicator changes it's horizontal alignment to indicate which level
> > it's going in...
> >
> > Anyone know how to determine the parent node of the indicated drop
> > position?
> >
> > thanks,
> > Thunder
> >
> >> > --- In flexcoders@yahoogroups.com <flexcoders%40yahoogroups.com>,
"Jonas
> > Windey" <jonas@> wrote:
> > >
> > > Hi,
> > >
> > >
> > >
> > > I have a tree with drag & drop enabled. Now what is the best way to
> > find out
> > > where the current selected item is dropped?
> > >
> > > I'd need to know its parent (if it's not on the rootnode), and the
> > position
> > > where it's dropped inside that parent.
> > >
> > >
> > >
> > > Or is there an easier way to find the position? Like comparing the
> > > dataproviders before & after?
> > >
> > >
> > >
> > > Thanks for the tips,
> > >
> > > Jonas
> > >
> >
> >
> >
>
__._,_.___
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
Web site design development Computer software development Software design and development Macromedia flex Software development best practice
YAHOO! GROUPS LINKS
- Visit your group "flexcoders" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
__,_._,___
Reply via email to