I can easily change it back. Hopefully Fred can describe his needs, or what has changed since earlier versions, so that I can come up with a solution that doesn't affect your code.
Good evening,
I'm glad to hear that this choice is not final!
If I can help Fred by any means I am present, even if only to describe how I adopted.
From my side it must find a way to restart the Shift and Ctrl keys that determine the movement or copying of nodes, not least as an option, which would meet both our cases!
I return in detail the problems encountered to date with the movement of nodes:
Consider KeepFocus.
Determine the current action: Move or Copy?
The selected node before DragNDrop.
Rehabilitate the tree if the action requested by the user is not authorized, is a big problem with moving node. I can detail if you wish. But the best solution is, in my opinion, can intervene in the action during the overflight of nodes (Forbidden / Allowed / Copy / Move).
For the reconstruction of nodes (tree), I found an interim solution, pending which I do not like.
To conclude it all, I am not able to distribute a demonstration program, but I can make you a video that might be more meaningful than the long text?
Thank you for everything.
Best regards.
(hope that google translate all correctly )