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?
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?
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...
Turkiyenin en sevilen filmlerinin yer aldigi xnxx internet sitemiz olan ve porn sex tarzi bir site olan mobil porno izle sitemiz gercekten dillere destan bir durumda herkesin sevdigi bir site olarak tarihe gececege benziyor. Sitenin en belirgin ozelliklerinden birisi de Turkiyede gercekten kaliteli ve muntazam, duzenli porno izle siteleri olmamasidir. Bu yuzden iste. Ayrica en net goruntu kalitesine sahip adresinde yayinlanmaktadir. Mesela diğer sitelerimizden bahsedecek olursak, en iyi hd porno video arşivine sahip bir siteyiz. "The Best anal porn videos and slut anus, big asses movies set..."