Interactivaly it doesn't work this.printStackTrace(), it prints nothing. The same can be said about console.trace() :-(
Modifying the source code is another approach, but it is more cumbersome. Fabian Jakobs-2 wrote: > > 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 > -- View this message in context: http://www.nabble.com/Long-stack-traces-tf3922256.html#a11135886 Sent from the qooxdoo-devel mailing list archive at Nabble.com. ------------------------------------------------------------------------- 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
