On Tue, 23 Feb 2010, thron7 wrote:
>> this.__data = [];
>> this.navTree.addListener("drop", function(e) {
>> this.__data = e.getTarget().someMethodOnMyWidget(); // returning an
>> array
>> rpc.callAsyn(callBack, 'remote method', this.__data);
>> }
>>
>> ...
>> Looking with the debugger it seems that it recurses (is this the right
>> verb?) in a check for callBack (?) being of type function.
>
> So what does callBack look like, then?
callBack = function(data, exc, id) {
if (exc == null) {
var text = data;
alert('callBack():' + data);
}
else {
alert(exc);
}
};
BTW, if instead of submitting the rpc call directly from the drop handler
doing so with a message bus handler (and dispatching a message from the drop
handler), everything works fine ...
Cheers,
Fritz
--
Oetiker+Partner AG tel: +41 62 775 9903 (direct)
Fritz Zaucker +41 62 775 9900 (switch board)
Aarweg 15 +41 79 675 0630 (mobile)
CH-4600 Olten fax: +41 62 775 9905
Schweiz web: www.oetiker.ch
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
