On Feb 12, 2008 6:46 PM, Andreas Junghans <[EMAIL PROTECTED]> wrote: > Hi, > > Am 12.02.2008 um 18:07 schrieb Derrell Lipman: > > > On Feb 12, 2008 11:59 AM, Gaetan de Menten <[EMAIL PROTECTED]> > > wrote: > >> Hi list, > >> > >> I've been having the following problem for quite a while: whenever I > >> throw an exception in a code which is executed in a callback of a > >> request, nothing noticeable happens, except the request just timeouts > >> ... > >> This seems to work fine but produces longer than necessary tracebacks > >> and also require me to modify all my callbacks. I'd like a global fix > >> or workaround. This might not be a Qooxdoo bug (I suspect it's rather > >> a firebug bug or missing feature), but nevertheless, has anybody > >> found a solution or another nicer workaround to this? > > I don't know which qooxdoo version you're using. In qooxdoo 0.6.x, > your error gets eaten (long story, I can get into it if you want me > to).
Yeah, I had a look at that discussion on the mailing list before posting, but since I verified the "fix" for that problem was in the version I use, I guess it's not the same problem (but it might be related -- I'll investigate some more if nobody comes up with a known solution/workaround). > In 0.7.x, you should see the error (at least from looking at the > code - I didn't try it). I'm running an 0.7.x checkout from yesterday, but as I said, it *might* (I just don't know yet) not be a qooxdoo bug. -- Gaëtan de Menten http://openhex.org ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
