On 19/9/00 11:38 pm, Geoff Canyon [EMAIL PROTECTED] wrote:
...is log any errors that occur in my program. In the past (in SuperCard) I
did this by locking error dialogs, and setting a handler at the top level
for the errorDialog message. The handler would dutifully write the
information on the error to the end of a property, which was later
exportable, in case I needed information to help debug a user's problem.
I don't do any specific error handling in this program. Most errors are
simple, non-fatal, and therefore I don't need to do specific error handling.
Given that, is there a reason to replace one lockErrorDialogs command, and
two handlers, with a ton of try...catch...end try constructs? I know
lockErrorDialogs is deprecated. Does that mean it's actually going away, or
just a recommendation against it?
Thanks in advance to those who register an opinion on this.
If its any help, the way we deal with this is to create a custom "execution
error" window. When there is an error, that window is opened and runs the
normal openCard / etc. scripts. It reads in, displays, and empties the
executionError property. You might want to consider this - you could
certainly have it log errors easily enough if you wanted too.
Regards,
Kevin
gc
Kevin Miller [EMAIL PROTECTED] http://www.runrev.com/
Runtime Revolution Limited (formerly Cross Worlds Computing).
Tel: +44 (0)131 672 2909. Fax: +44 (0)1639 830 707.
Archives: http://www.mail-archive.com/metacard%40lists.best.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to [EMAIL PROTECTED], not this list.
