Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!tut.cis.ohio-state.edu!rutgers!njin!princeton!phoenix!pucc!SEB
From: SEB@pucc.Princeton.EDU (Scott E Barron)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: Deleting Cards Unintentionally
Message-ID: <6004@pucc.Princeton.EDU>
Date: 30 Aug 88 12:45:58 GMT
References: <13631@agate.BERKELEY.EDU> <65844@sun.uucp> <16219@apple.Apple.COM> <2815@pt.cs.cmu.edu> <16309@apple.Apple.COM>
Reply-To: SEB@pucc.Princeton.EDU
Organization: Princeton University, NJ
Lines: 26
Disclaimer: Author bears full responsibility for contents of this article

In article <16309@apple.Apple.COM>, dan@Apple.COM (Dan Allen) writes:
 
>In article <2815@pt.cs.cmu.edu> tgl@zog.cs.cmu.edu (Tom Lane) writes:
>>2.  How come the "can't delete" bit for backgrounds and cards is not
>>    a scriptable property?
>
>Good question.  Look for it in a future release.  A script should be
>able to get and set the "can't delete" bit.
>
>Dan Allen
>Apple Computer
 
As I understand it, Hypercard 1.2.1 has a new property that allows the
"can't delete" bit of a card or background to be set from a script.  It
is the cantDelete property.  An example is:
 
set cantDelete of this cd to true
            or
set cantDelete of this bg to true
         or even
set cantDelete of this stack to true
 
 
I have used this property in several scripts and it works quite well.
Is this correct, Dan?
 
-------------------------------- SEB -----------------------------------