Phil-
Wednesday, June 17, 2009, 2:20:03 PM, you wrote:
So my question is:
When 'errorDialog' is executed, is its executionError parameter (which
contains error description info) the only data that's available to help
us get at the cause of the error? I can live with that, but I would just
Someone please educate me...
My current understanding of the debugContext is this: it provides access
to any context listed in the executionContexts and to no other contexts.
To access a context other than the current one, you set the debugContext
to the number of the line in the
I should have said - I'm assuming the standalone environment in all this.
Phil
Phil Davis wrote:
Someone please educate me...
My current understanding of the debugContext is this: it provides
access to any context listed in the executionContexts and to no other
contexts. To access a
Phil-
I'm out of town at the moment without access to my notes or code, but
I believe you're correct about this. To my recollection the traceError
and errorDialog messages are mutually exclusive (one happening when
debug mode is on and the other when it's off) and the errorDialog
message doesn't
Thanks Mark.
Mark Wieder wrote:
Phil-
I'm out of town at the moment without access to my notes or code, but
I believe you're correct about this. To my recollection the traceError
and errorDialog messages are mutually exclusive (one happening when
debug mode is on and the other when it's off)
