bump bump anyone"?

Yes, the event is indeed publicly not exposed. I suppose that the Reddy used BeforeBeginNodeEdit (first he enabled node editing) - this fires on double click and always returned true from the event handler (returning true cancels the edit event). He then proceeeded with the workaround I suggested.

I think this could probably work.

 i tried using the beforebeginnodeedit client side event, 

and returned true,

after i double click on a node, the text on that node dissapears any idea why that might be?

 I see the same results (disappearing text).

So this does indeed work for capturing the double-click, but I'll now have to try to capture text and replace so that it doesn't disappear.

Thanks as always for your assistance.

Dan

PS - Glad I could edit my post - I didn't pay enough attention and didn't return true, thereby making the text editable (not desirable).

Did you come up with a way to prevent the disappearing text?  I need the allow double-click, but I also need the text to remain.

Hmmm - this was 6 mos. back, but digging into my code I see that I have the following:

// turn off edit capability of tree

function igtree_beginedit(tn, nodeId) {

//custom logic here

return false;

}

So capture the event and return false to disable the editing.

Dan