At 17:39 +0100 07/16/2002, Paul Fletcher wrote:
>Also another idea might be to use the 'alert hook' and put in a handler to
>create a text or ini file to store the error that is occuring. This way you
>can view what is causing the problem when it crashes!
Well, that'll work if it's a Director generated error. However, if
it's a system problem (that's the only way I can think offhand that a
kiosk would also shut down), alertHook won't yield anything fruitful.
Still, its a good suggestion and would certainly trap anything
internal to the program. I'd simply forgotten aobut it.
--
Warren Ockrassa | http://www.nightwares.com/
Director help | Free files | Sample chapters | Freelance | Consulting
Author | Director 8.5 Shockwave Studio: A Beginner's Guide
Published by Osborne/McGraw-Hill
http://shop.osborne.com/cgi-bin/osborne/0072195622.html
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/lingo-l.cgi To post messages to the list, email
[EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for
learning and helping with programming Lingo. Thanks!]
