1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
|
---
title: tree.move
name: event-tree-move
---
Triggered when the user moves a node.
Note that this event is called **before** the node is moved. See note about `do_move` below.
Event.move_info contains:
* moved_node
* target_node
* position: (before, after or inside)
* previous_parent
{% highlight js %}
$('#tree1').tree({
data: data,
dragAndDrop: true
});
$('#tree1').bind(
'tree.move',
function(event) {
console.log('moved_node', event.move_info.moved_node);
console.log('target_node', event.move_info.target_node);
console.log('position', event.move_info.position);
console.log('previous_parent', event.move_info.previous_parent);
}
);
{% endhighlight %}
You can prevent the move by calling **event.preventDefault()**
{% highlight js %}
$('#tree1').bind(
'tree.move',
function(event) {
event.preventDefault();
}
);
{% endhighlight %}
You can later call **event.move_info.move_info.do_move()** to move the node. This way you can ask the user before moving the node:
{% highlight js %}
$('#tree1').bind(
'tree.move',
function(event) {
event.preventDefault();
if (confirm('Really move?')) {
event.move_info.do_move();
}
}
);
{% endhighlight %}
Note that if you want to serialise the tree, for example to POST back to a server, you need to let tree complete the move first:
{% highlight js %}
$('#tree1').bind(
'tree.move',
function(event)
{
event.preventDefault();
// do the move first, and _then_ POST back.
event.move_info.do_move();
$.post('your_url', {tree: $(this).tree('toJson')});
}
);
{% endhighlight %}
|
