> Could you explain how does this tracing work? Does this work in IE,
> too?
As far as I could see it won't as the IE exception doesn't include any stack
information. It's only available in Gecko/FF.
Til, I can see that formatLogEvent would do the trick, showing a string, object
(with all prop
Sebastian Werner schrieb:
Could you explain how does this tracing work? Does this work in IE, too?
It only works in Firefox.
First it is important to pass the exception object to the logger. So I
patched all catch-blocks in my local qooxdoo version to do so.
In firefox exception objects hav
Hugh Gibson schrieb:
Would it be possible to improve the error message given above to include the fileName and lineNumber from the exception (available in FF/Gecko and perhaps others), so that developers have a better indication of where to look? It's in QxTarget.js, _dispatchEvent. I put in
Til Schneider schrieb:
Hugh Gibson schrieb:
Would it be possible to improve the error message given above to
include the fileName and lineNumber from the exception (available in
FF/Gecko and perhaps others), so that developers have a better
indication of where to look? It's in QxTarget.js, _di
Hugh Gibson schrieb:
We just got bitten by a bug in our code. It was in an event handler. There was
a red error message in the debug output, but very little indication of the
fault:
QxGetRequest[HASHCODE:574]
015002:Failed to execute "_dispatchEvent()":Could not dispatch event of
type "comple
We just got bitten by a bug in our code. It was in an event handler. There was
a red error message in the debug output, but very little indication of the
fault:
QxGetRequest[HASHCODE:574]
015002:Failed to execute "_dispatchEvent()":Could not dispatch event of
type "completed":Expected identifi
