How to cancel a drop after an Ajax failure

[gr_great_2000]

Hello everybody,

I cannot cancel a drop event after an Ajax failure, e.g.

function dropHandler(dropEvent) {
...
dropEvent.cancel = false;
Ext.Ajax.request {
...
failure: {
dropEvent.cancel = true;
alert("On failure: "+dropEvent.cancel);
}
}
alert("After request: "+dropEvent.cancel);
}

First the "After request: false" message is printed, then the "On failure: true" but it is late. How can I affectively cancel the drop on ajax failure? Any tips?

Thanks in advance
George

[jay@moduscreate.com]

George,


What UI widget are you using?

[Animal]

Asynchronous!

[gr_great_2000]

I guess I am using asynchronous widgets. I use nodeType: 'async' in my trees, if this is what you are asking. I understand the fact that ajax request is asynchronous, but how can you handle such cases when you want to cancel a drop after an synchronous ajax request?

[Animal]

You can't! The drop happened aeons (In processor time) before the Ajax request creeps back along the wire!

[jay@moduscreate.com]

I would say, return false from onNotifyDrop, cache the drop event, if the ajax event is successful, complete the drop. I've done this before and it works.

[gr_great_2000]

Thanks for your help! I will try to implement what your are suggesting.

[gr_great_2000]

I tried to follow your instructions but it didn't work. Maybe I didn't do it properly. When an 'beforenodedrop' event is fired at my tree, the handler -that it is called- does not wait for Ajax to return (either success or failure). When this function returns, game is over (no matter if I cache the event and try to fire the event again or call some other function). Am I missing something here?

[Animal]

Yes.

You have to forget about the drop doing the business.

record what is being dropped where. CANCEL the drop event.

Then, in your Ajax success handler, perform the removal of the dragged "thing" (was it a treenode, I forgot), and the addition to wherever the drop point was.

[gr_great_2000]

Thank you both Jesus and Animal for your help! I think that you -more or less- say the same thing. But you helped me a lot to figure out a solution to this:

I always return true in case of a valid drop. I also cache the drop event and in case of an Ajax failure, I just remove the node that has been dropped (special care needed for the node ids). I could also do it the other way around. Always reject a drop, but in case of an ajax success to add the drop node. It turned out to be easier than I thought...