1 Answer, 1 is accepted
0
Hi icebits,
Actually, we omitted to include this event in the help manual. It is fired right after the node-editing has finished.
There are two client-side events associated with the node-editing:
OnClientNodeEditing and OnClientNodeEdited.
The first one (OnClientNodeEditing) is fired while a TreeNode is being edited. You should hook on this event to obtain the old and new text of the node, like:
function OnClientNodeEditing(sender, args)
{
var node = args.get_node();
var oldText = node.get_text();
var newText = args.get_newText();
}
Hope this helps.
The needed help articles will be added right away. These articles will be included in the forthcoming SP1 release due by the end of the week.
Sincerely yours,
Nick
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Actually, we omitted to include this event in the help manual. It is fired right after the node-editing has finished.
There are two client-side events associated with the node-editing:
OnClientNodeEditing and OnClientNodeEdited.
The first one (OnClientNodeEditing) is fired while a TreeNode is being edited. You should hook on this event to obtain the old and new text of the node, like:
function OnClientNodeEditing(sender, args)
{
var node = args.get_node();
var oldText = node.get_text();
var newText = args.get_newText();
}
Hope this helps.
The needed help articles will be added right away. These articles will be included in the forthcoming SP1 release due by the end of the week.
Sincerely yours,
Nick
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center