Bug 4780 ... I took the liberty to assign it a priority P2 and a target 1.4 ... the Qooxdoo team will reset as approriate anyway ...
As Derrell said, it should probably be easy and I think it can save a lot of time to the developer, especially the less experienced ones, in an area that is not that easy to get right at the beginning (rpc calls). Cheers, Fritz On Tue, 15 Mar 2011, Derrell Lipman wrote: > On Tue, Mar 15, 2011 at 09:46, Fritz Zaucker <[email protected]>wrote: > >> the following scenario seems more difficult to debug than it could be: >> >> I have rpcAsync call that returns without error from the backend, e.g. >> exc >> is NULL. >> >> Within the callback of this rpcAsync() call I had a runtime error >> (trying to call some method on an undefined variable): >> >> myHandler: function(dataNew,exc,id) { >> if (exc == null) { >> var test; >> test.setValue(5); // runtime error from this >> } >> else { >> alert(exc); >> } >> >> >> The result was, I believe, that myHandler was called again, this time with >> exc set and resulting in something along the line "Local error 2". >> >> I don't quite understand was is going on, but to the unsuspecting user (as >> myself) it looked as if the backend did return an error (which it didn't). >> >> I think it would be helpful if runtime errors in the callback would be more >> easily be detectable (for example, by including a stack trace). >> > > This has come up a number of times. Having thought about it, I believe it > should be easy to fix with a try/catch block around the call to the user's > callback. Please create a bugzilla entry. This should get fixed. > > Thanks, > > Derrell > -- Oetiker+Partner AG tel: +41 62 775 99 03 (direct) Fritz Zaucker +41 62 775 99 00 (switch board) Aarweg 15 +41 79 675 06 30 (mobile) CH-4600 Olten fax: +41 62 775 99 05 Schweiz web: www.oetiker.ch ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
