Last Updated: 22 May 2017 16:32 by Yehudah
Last Updated: 23 Jan 2017 07:04 by ADMIN
The default value of the DragDropManager.TouchDragTrigger attached property is not respected. The default value is TapDown, but the touch drag starts on tap hold and move.

Since the 2017 R1 (2017.1.117) release the DragDropManager.TouchDragTrigger property is obsoleted. Use the TouchManager.DragStartTrigger property instead.
Last Updated: 03 Jan 2017 21:05 by ADMIN
Adding dragOrder binding property on DragBehavior which support items reorder, so that items that are bound to Services/Database can be reordered.

The responsibility for reordering items on the server side should be taken by the developer, via mediator class-es that handle the reordering, or in a multi- layer abstraction able to handle the logic.
Last Updated: 29 Mar 2016 06:50 by ADMIN
Available in LIB version 2016.1.328, it will be also available in the 2016 R2 release.
Last Updated: 08 Feb 2016 15:51 by Levent
If you have attached ContextMenu(RadContextMenu) to an element and you have added logic to drag this element with DragDropManager, when you open the ContextMenu and click on the element, a new DragOperation is started (it should just close the ContextMenu).

Available in LIB version 2016.1.208, it will be also available in the 2016 Q1 SP1 Release.
Last Updated: 06 Jul 2015 13:56 by Sun
After resizing the Window the buttons start working, but if dragged n dropped again, they stop.
Last Updated: 29 May 2015 11:16 by ADMIN
Created by: Steven
Comments: 3
Category: DragDropManager
Type: Bug Report
I have developed a UI with features of Drag and drop from RadGridView to RadTreeView, it worked perfectly in old version (2011 Q3), after I upgraded to new version (2014 Q4), I got a warning message for the RadDragAndDropManager because of obsolete and the drag & drop cannot work now. My question is whether I must upgrade RadDragAndDropManager to DragDropManager suggested by some articles, or I still can use the RadDragAndDropManager without affecting the exsiting features. 
Please refer to attachment for details.