Peter, as Richard said, stack corruption is rare but if you truly want to check this kind of stuff, why not use a simple try/catch block?
try go stack "I am as corrupt as the brazilian goverment" catch n answer error "the stack is dizzy" end try this will make sure the stack is actually a stack but it can't verify if the stack content is right, you might want to do further checks. If your stack never changes, you can compute a checksum from the stackfile and store it somewhere for comparing. Andre On Mon, Jul 28, 2008 at 5:48 AM, Peter Alcibiades <[EMAIL PROTECTED]> wrote: > What do people usually do when launching an app using a splash stack, to check > if the main stack successfully opens? > > Do you use try, or do you write a custom error handler? > > I am wondering how to take care of the case of main stack corruption. I'd > like to have something that if the stack doesn't load, it does a series of > things to restore from the ~ file. > > How do people usually do this? > > Peter > _______________________________________________ > 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 > -- http://www.andregarzia.com All We Do Is Code. _______________________________________________ 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