Beta 2.0 - Bugs 'n' stuff
rbarber at yhb.att.ne.jp
Wed Apr 9 02:27:01 EDT 2003
This will sound stupid, but I found a use for it.
I have a script that puts info about the selectedfld of the topstack when it
opens. Not all of my topstacks have flds and I'm forever getting 'no such
object' error messages when working with that stack or stacks related to it.
I commented out the offending line but then forget to uncomment it when I
make builds. Checking the suppress error btn lets me work with that stack a
little easier. This use is not by design, I don't recommend it because it
doesn't catch the other errors so you don't write with suggestions on how to
deal with my approach ;) You asked when you don't want to know when its
broken - when you (already) know its broken, I guess.
> From: Ken Norris <pixelbird at interisland.net>
> Reply-To: use-revolution at lists.runrev.com
> Date: Tue, 08 Apr 2003 22:57:12 -0400
> To: <use-revolution at lists.runrev.com>
> Subject: Re: Beta 2.0 - Bugs 'n' stuff
>> Date: Tue, 08 Apr 2003 10:40:53 -0800
>> Subject: Re: Beta 2.0 - Bugs 'n' stuff
>> From: Richard Gaskin <ambassador at fourthworld.com>
>> This thread reminds me: There's a button in the toolbar to suppress error
>> warnings -- under what circumstances would you not want to know that your
>> script is broken?
> Ditto. I wondered the same thing.
> Ken N.
> use-revolution mailing list
> use-revolution at lists.runrev.com
More information about the Use-livecode