Hi David, if you know where the error occurs you can add a call to printStackTrace at the position where you want to see the stack trace:
this.printStackTrace(); This function is new in 0.7 and is defined here: http://demo.qooxdoo.org/current/apiviewer/#qx.log.MLogging#printStackTrace Best Fabian > When debugging with Firebug, how do you deal with long stack traces? > In Firebug 1.0, only the last 10 or so can be accessed (depending on the > resoution of your screen). > Call stacks can be very nested in qooxdoo. > > I complaint to the author of Firebug long ago, but it hasn´t been solved. > Any workaround? > Thanks for sharing any trick. > > Regards, > David > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
