Re: errorDialog, executionContexts, debugContext
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 like to know. Or am I missing something? Can you handle the traceError message instead (put this into a frontscript)? on traceError pHandlerName, pLineNumber, pCharOffset, pErrorInfo, pObjectID, pErrorType answer got traceError put executionContexts= the executionContexts cr after msg set the debugContext to line 1 of the executionContexts --put debugContext= the debugContext cr after msg debugdo put the variableNames cr after msg debugdo put myVar cr after msg set the debugContext to empty pass traceError end traceError -- -Mark Wieder mwie...@ahsoftware.net ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
errorDialog, executionContexts, debugContext
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 executionContexts that describes the context you want to access. (And to return to the original context you set it to empty.) If this is true, then it apparently can't be used in an 'errorDialog' handler to get info about variables in the code where the error occurred. That's because the executionContexts gets reset to show the 'errorDialog' handler as the only context. It seems to work this way whether the errorDialog handler is in the offending script or in a different one further along the message path. 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 like to know. Or am I missing something? Like I said, someone please educate me! Thanks to all. -- Phil Davis PDS Labs Professional Software Development http://pdslabs.net ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: errorDialog, executionContexts, debugContext
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 context other than the current one, you set the debugContext to the number of the line in the executionContexts that describes the context you want to access. (And to return to the original context you set it to empty.) If this is true, then it apparently can't be used in an 'errorDialog' handler to get info about variables in the code where the error occurred. That's because the executionContexts gets reset to show the 'errorDialog' handler as the only context. It seems to work this way whether the errorDialog handler is in the offending script or in a different one further along the message path. 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 like to know. Or am I missing something? Like I said, someone please educate me! Thanks to all. -- Phil Davis PDS Labs Professional Software Development http://pdslabs.net ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: errorDialog, executionContexts, debugContext
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 have the context. I'll check when I'm back in town. -- -Mark Wieder mwie...@ahsoftware.net ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: errorDialog, executionContexts, debugContext
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) and the errorDialog message doesn't have the context. I'll check when I'm back in town. -- Phil Davis PDS Labs Professional Software Development http://pdslabs.net ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
