Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!jkc
From: jkc@Apple.COM (John Kevin Calhoun)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: Hyper Mystery
Keywords: buttons, hilite, mystery
Message-ID: <52591@apple.Apple.COM>
Date: 8 May 91 17:24:52 GMT
References: <142454.21886@timbuk.cray.com>
Distribution: na
Organization: Apple Computer Inc., Cupertino, CA
Lines: 34


In article <142454.21886@timbuk.cray.com> kunau@eiger.cray.com
(Tim Kunau) writes:
>
>       Hyper Mystery - by Peter Fleck
>
>  The new HyperCard features slicker stack and card designs
>  than the old one. An example is the Home Card with its neat
>  navigation buttons across the bottom of the card.
>  
>  I decided to add similar buttons to a stack I was creating and
>  began looking for the scripting that controls the hiliting of 
>  these buttons as you travel from card to card in the Home stack.
>
>  What I discovered was that there is no command for setting those
>  hilites!
>  
>  Who/What sets the hilites for the navigation buttons?
>

I passed this along to Robin Shank, who was the chief stack designer for
HyperCard 2.0.  Here's her answer:

"Actually, the hilite states of the buttons along the bottom of the
2.0 Home stack do not need to be set on open/close card. They're bkgnd
buttons with sharedHilite FALSE, with the hilite of each button true only
on it's corresponding card.   Originally there were scripts to hilite the
buttons on openCard and closecard, but when we got the sharedHilite property,
it eliminated the need to do that - the buttons stay hilited independently
all the time with no need to script them.  SharedHilite is useful for
things other than radio buttons and check boxes."

Kevin Calhoun
jkc@apple.com