Hey,
in general a good idea but this error is thrown by qx.core.Object using the
bootstraps error method. So using the stacktrace there would bring in a new
dependency (I guess) which is not good at that level.
Best,
Martin
Am 21.09.2010 um 11:06 schrieb panyasan:
>
> Hi Martin,
>
> thanks
Hi Martin,
thanks for the clarification. But wouldn't it make more sense in theses
cases to automatically print a qooxdoo-stacktrace using qx.dev.StackTrace
(I don't remember the correct class name) instead of letting the error be
handled by the javascript engine (which produces these unusable s
Hello Christian,
I would just break on that error (using chrome or safari which works good for
me) and check the classname of the object not having that property. I guess it
comes from a loaded model object so the class name could tell you some more
details about whats actually in the class its
Hi list,
one cool aspect of qooxdoo is all the magic behind the property system: the
automatic setter/getter, validation and value application support etc. The
downside to the convenience this all brings is that the machinery behind is
quite complex and sometimes makes debugging difficult if some
