Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!pasteur!ames!oliveb!apple!stadler
From: stadler@Apple.COM (Andy Stadler)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: Copying a background (hacker's tip & request for feature)
Message-ID: <30366@apple.Apple.COM>
Date: 9 May 89 18:05:45 GMT
References: <445@nyevax.CAS.ORST.EDU> <2667@osiris.sics.se>
Organization: Apple Computer Inc, Cupertino, CA
Lines: 17

In <many articles> <lots of people> write:

>  [There's no good way to change bkgnd's, bkgnd data, associate cards
>   with given bkgnds, etc, etc]

There are unfortunately other problems with simply "assigning" arbitrary
card and background combinations.  A card and a background aren't just two
independent layers!  A card is built on top of a background.  For example,
a background field has text stored in the card on a card by card basis.
I'm not saying it's impossible to stick any card with any background, but
there are many potential problems involved.

What I'd like to hear is, what level of power-user-tool vs. stack integrity
are you (a reasonably high-power set of users from reading these messages)
interested in?

--Andy           stadler@apple.com