Telerik Team,
Using the RadDragAndDropManager, in ExecutionMode = Legacy with the latest DLLs, if I drag an item out of the browser, and drop it out of the browser, the drop never registers. So when I move the mouse back onto the browser, the drag operation is still in effect even though the mouse button is not pressed.
I can solve this problem by using .MouseCapture() in the OnDragQuery handler. Thus, when the button is released off screen, the drag operation is abandoned properly.
However, this technique does not work in ChildWindows. Even if I add the ChildWindow or the ListBox to the args.Options.ParticipatingVisualRoots. In fact, using .MouseCapture() at all in the OnDragQuery handler stops all drag and drop functionality even though I used the exact same code as in a non-child window.
Is there a more proper way of handling drops that occur off-screen for ChildWindows?
If I can upload a complete project if that would help.
Thanks!
Using the RadDragAndDropManager, in ExecutionMode = Legacy with the latest DLLs, if I drag an item out of the browser, and drop it out of the browser, the drop never registers. So when I move the mouse back onto the browser, the drag operation is still in effect even though the mouse button is not pressed.
I can solve this problem by using .MouseCapture() in the OnDragQuery handler. Thus, when the button is released off screen, the drag operation is abandoned properly.
However, this technique does not work in ChildWindows. Even if I add the ChildWindow or the ListBox to the args.Options.ParticipatingVisualRoots. In fact, using .MouseCapture() at all in the OnDragQuery handler stops all drag and drop functionality even though I used the exact same code as in a non-child window.
Is there a more proper way of handling drops that occur off-screen for ChildWindows?
If I can upload a complete project if that would help.
Thanks!