>If I understand this discussion correctly the need is for a mechanism of
>"duplicating" objects with all their properties script included. Scott I
>think mentioned "shareScript" which makes a lot of sense.
>Generally speaking I can see the usefulness of "shareProps" as well which
>would allow making changes to the duplicated object to appear in the
>duplicates as well. This of course must be limited or take parameters [set
>shareProps(textFont,backgroundColor,script,etc.) to true/false]. A script
>would look something like this:
>
>set shareProps(textFont,backgroundColor,script) of fld X of stack S to true
>duplicate fld X of stack S in card 2 of this stack
Andu,
I hate this syntax. Why don't we just add a new property "the
sharedProperties" which contains a list of the properties that are shared:
set the sharedProperties to "loc, rect, highlight, text"
set the sharedProperties to empty -- all are card-local
set the sharedProperties to the properties of me -- all are shared
This is much more xTalk-y. BTW, do we already have "the properties"
property in MC? HC has this for its xWindows, and it's the most sensible
choice.
Cheers,
-- M. Uli Kusterer
------------------------------------------------------------
http://www.weblayout.com/witness
'The Witnesses of TeachText are everywhere...'
--- HELP SAVE HYPERCARD: ---
Details at: http://www.hyperactivesw.com/SaveHC.html
Sign: http://www.giguere.uqam.ca/petition/hcpetition.html
