[Solved] Cannot drop on node

[Rainer Friedl]

Hello,

I have a TreeView where both is enabled:
DragAnDrop + DragAndDropBetweenNodes

Then, I connaot drop ON a node (the server side event always is set to DropPosition = Below)

If only one of the Drags is enabled, it as it is supposed to do.

By the way: is there a client side property in the 'args' where I can read out the drop position? I did not find one.

Kind regards,
Rainer

[Dimitar Milushev]

Hello Rainer,

The server event NodeDrop reports the proper drop position according to our tests. Please find attached a sample project that shows this functionality.

There is currently no direct way to get the drop position from the client-side event arguments. Such a property is a good idea and I'll make sure to log it as a feature request.

Regards,
Dimitar Milushev
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

[Rainer Friedl]

Hello,

thanks for your reply.

Maybe it is not possible for me to drop on nodes, because I am using a NodeTemplate?

I tried a lot now, but it keeps what I have written: If both Drag modes are enabled, the DropPosition is never 'Over'.

[N]

Hi Dimitar,

There is currently no direct way to get the drop position from the client-side event arguments. Such a property is a good idea and I'll make sure to log it as a feature request.

The property DOES exist, but it doesn't work!

This is not good. I just spend a day converting code from the old radTreeview to the new Prometheus version. I don't recommend this conversion to anyone who uses a lot of client-side manupilation.  The old radTreeview implements  the client-side dropPosition property perfectly.The new Prometheus version is actually better than the old one at showing you the "above" or "below" position (dotted line) while you're dragging and also contains the client-side dropPosition property but this property always returns 'undefined':

function onNodeDropping(tree, args) {

  var dropPosition = args.get_dropPosition();
  //dropPosition is always 'undefined' !!!
...

}

Why have you implemented the property if it will never be assigned a value?
This is not good for my project.

[Dimitar Milushev]

Hello Nuri,

As I mentioned at the end of this thread, the problem you are experiencing was a bug in the current implementation. If this is vital for your project, please open a support ticket and we will send you the latest "Prometheus" build that includes this fix.

Best wishes,
Dimitar Milushev
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center