Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!brunix!eilat!man
From: man@eilat.cs.brown.edu (Mark H. Nodine)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: Query: Card Buttons vs Background Buttons
Message-ID: <45766@brunix.UUCP>
Date: 25 Jul 90 14:51:47 GMT
References: <685@cvbnetPrime.COM>
Sender: news@brunix.UUCP
Reply-To: man@eilat.cs.brown.edu (Mark H. Nodine)
Distribution: na
Organization: Brown Computer Science Dept.
Lines: 39

In article <685@cvbnetPrime.COM>, aperez@caribe.prime.com (Arturo Perez
x6739) writes:
|>I've put together this stack for personal use and I keep running into this
|>problem with background buttons.
|>
|>If you put a background radio or checkbox button on a card then when you
|>make a new card, it appears on the new card.  But if you hilite the button
|>then ALL the radio buttons in the stack get hilighted.
|>
|>If you turn it into a card button, then it doesn't get copied automatically.
|>
|>So, what am I missing here?

Sounds like you're not missing anything.  That's the way it works.  On
the other hand, you probably want to keep a different highlight state
for each card in the stack.  To do this, you need to create a background
field, say "state", which you hide.  A background field, unlike a
button, has a different contents on each card in the background.  Then
what you need to do is put the following into your background script
(I'm illustrating this for a checkbox for simplicity instead of a radio
button group):

  on openCard
    set the hilite of bg btn "Button" to bg fld "state"
  end openCard

and in the button's script
               
  on mouseUp
    set the hilite of me to not the hilite of me
    put the hilite of me into bg fld "state"
  end mouseUp

That way, when you go to a new card, the button's state will be
automatically set to what it was the last time.  (You may have some
initialization problems when you create new cards, but these are easily
dealt with.)

	--Mark