Sorry about that - I just did not have the time to document all
events. I figured most of the time a console.log(data.rslt) would
suffice. Well, not always, as for example the move_node is a bit
harder to "decode" - it is in the core docs - bottom of the page:

.o - the node being moved
.r - the reference node in the move
.ot - the origin tree instance
.rt - the reference tree instance
.p - the position to move to (may be a string - "last", "first", etc)
.cp - the calculated position to move to (always a number)
.np - the new parent
.oc - the original node (if there was a copy)
.cy - boolen indicating if the move was a copy
.cr - same as np, but if a root node is created this is -1
.op - the former parent
.or - the node that was previously in the position of the moved node

I will try and update the docs with information regarding events. As
for the data object as a whole (not only data.rslt) (again from the
core docs):

           "inst" : /* the actual tree instance */,
           "args" : /* arguments passed to the function */,
           "rslt" : /* any data the function passed to the event */,
           "rlbk" : /* an optional rollback object - it is not always present */

Most functions that actually can be rolled back provide the rlbk
property. I guess if you need it - just see if your function provides
the rlbk. If I missed it - just tell and I will add it, but I do not
believe I missed it anywhere. It is present with all modifying
functions, with a few exceptions (like select_node, check_node, etc)
as the exceptions have opposite functions (like deselect_node,
uncheck_node, etc).

'개발 > jQuery 플러그인 메뉴관련' 카테고리의 다른 글

jsTree onselect & onclick events  (0) 2011.04.12
jsTree(jQuery)  (0) 2011.04.07

+ Recent posts