well, there is a stack-trace. But you won't like it;) We use one large 'custom.js' that contains all qooxdoo classes we need but it has gone through the generator script and therefore isn't very user-friendly.
May I send it to you diretly as it's ~ 1 MB in size and zip files are rejected by sourceforge? Rüdiger Fabian Jakobs wrote: > Rüdiger Herrmann schrieb: >> Fabian, >> >> this Problem didn't occure in previous versions. Neither in 0.7 nor in >> 0.6.5 (the version we are currently migrating from). >> The combination of widgets is rather complex (see >> http://rap.innoopract.com/rap). I am currently trying to strip it down - >> will keep you informed. >> > Do you get a stack trace after the error message? This will not work in > IE but at least in FF you should get the stack trace, to see where the > problem comes from. If you don't get a usble stack strace try to remove > the try statement around this code at qx.ui.core.Parent.js:1288 > > // WRAP TO LAYOUT ENGINE > try { > this.getLayoutImpl().layoutChild(vChild, vChanges); > } catch(ex) { > this.error("Could not layout child " + vChild + " through layout > handler", ex); > } > > And inspect the error in the FireBug console. > > > Best Fabian > ------------------------------------------------------------------------- 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 qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
