Hi Daniel,
I've modified the error message in two ways:
1. Add the classname of the ui object causing the exception in
qx.ui.core.queue.Appearance line 98:
qx.log.Logger.error(qx.ui.core.queue.Appearance, "Error in
the 'Appearance' queue: obj.classname: " + obj.classname + ", " + ex, ex);
2. Added a check in qx.theme.manager.Decoration in method addCssClass in
line 91 if the given decorator is resolvable
if(!instance) {
throw new Error(' unable to resolve CSS class for decorator "'
+ value + '"');
}
With this I'm perfectly able to locate what was going wrong. I was
simply missing a decorator in my theme.
And yes, of course, your right. It is/was possible to find the problem
using the chrome debugger.
The changes above should be considered. I think there worth being applied.
Regards
Dietrich
Am 10.07.2013 10:30, schrieb Daniel Wagner:
> Hi Dietrich,
>
> I agree, these messages don't really help. You can disable the
> qx.debug.ui.queue environment setting and activate the "pause on
> uncaught exceptions" option in Chrome's dev tools. I don't know about
> you, but I'd rather live debug an app than read through a huge,
> elaborate error message;-)
>
> Regards,
> Daniel
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
