Thank you for your feedback and thoughts, guys, we will keep them in mind.
Regards,
Marin Bratanov
Progress Telerik
Hi,
To me it is important to also reparent.
The jquery version feels more intuitive.
Regards,
Erik
The primary use case is not reparenting, but rather reordering. The jQuery version does exactly what's needed.
It would suffice for us to be notified that node X has been moved. It would be helpful to be told whether it was a reorder or reparent, to know how much of the tree to potentially renumber.
Our documents are typically numbered with a scheme such as:
A.1
A.1.1
or
AC-1
AC-1.a
etc.
When a user drags a node to a new location we will renumber the items to correspond. This potentially affects an entire subtree, so it's helpful to be able to minimize the db calls needed.
Hello Jon,
To make sure we're on the same page, which approach would you prefer:
It is possible that the functionality like in React would be a v1 and what is available in jQuery would be v2, but at this point I can't say, so I am gathering your preferences and needs.
Regards,
Marin Bratanov
Progress Telerik
I'm pleasantly surprised to get a response so quickly.
If I recall I was unable to give visual feedback while dragging in WinForms, but I think this would be preferable to the context menu. Once you start dragging to the target location, you should be able to get visual feedback about:
It will be inserted at the same tree level, either before or after the target.
It will be inserted as a child of the target.
Hello Jon,
Thank you for your feedback.
I expect the first version to report the new parent. You can track a context menu here, yet I am not sure an integration on drop would be easy or even possible when it becomes available. We will keep your idea in mind for sure, maybe an option where a node gets dropped may be available in blazor even if not through a context menu, we will see what is possible when research starts.
Regards,
Marin Bratanov
Progress Telerik
Our WinForms implementation uses a context menu to support
on drop. It would be great if this were possible. We have the tree bound to a tree data manager with rules for how to auto-number the items since ours normally have hierarchical header numbering. But if you just reported that an item was moved, perhaps with the old parent and the new parent, we could handle it.