My favorites | Sign in
Logo
             
New issue | Search
for
| Advanced search | Search tips
Issue 246: When drag_copy rule is "on" the onmove callback is not called in a multitree drag&drop operation
1 person starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  ivan.bozhanov
Closed:  Nov 11
Type-Defect
Priority-Medium


Sign in to add a comment
 
Reported by frankisans, Oct 15, 2009
What steps will reproduce the problem?
1. Define two trees  A and B with multitree "all". Set drag_copy to "on" on B
2. Define a onmove callback on both trees
3. Drag a node from B to A. The onmove callback is not called.

What is the expected output? What do you see instead?
The check_move callback is allways called, it works as expected.

What version of the product are you using? On what browser?
The last one 0.9.9. On google chrome.

Please provide any additional information below.

Comment 1 by ivan.bozhanov, Nov 11, 2009
Thank you - drag'n'drop and move has been completely rewritten on my working copy so
this is fixed.
Status: Fixed
Owner: ivan.bozhanov
Sign in to add a comment

Hosted by Google Code