Bob Sneidar wrote: > In FoxPro you could simply create a handler which got triggered by > errors then check an internal code for what the most recent error > was, then make a switch statement to handle all the pertinent errors > for your project. The normal error message display was suppressed so > that the developer could present a message of his own and then act > accordingly. For example, database connection errors could drop into > a repeat loop asking the user to try again or quit. I think this > would be a preferable method to try/catch because all your error code > could be consolidated into one place.
That's pretty much what LiveCode offers with the errorDialog message. -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ____________________________________________________________________ ambassa...@fourthworld.com http://www.FourthWorld.com _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
