Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!psuvax1!ukma!seismo!esosun!smithey
From: smithey@esosun.UUCP (Brian Smithey)
Newsgroups: comp.sys.amiga.programmer
Subject: Boolean Gadget Mutual Exclusion?
Message-ID: <659@esosun.UUCP>
Date: 31 Jan 91 18:46:58 GMT
Reply-To: smithey@esosun.css.gov.UUCP (Brian Smithey)
Organization: Science Applications International Corp., San Diego
Lines: 29

I want to create a set of "radio buttons", where only 0 or 1
button of the set is selected at any one time.  I figured
to do this with TOGGLESELECT boolean gadgets, and when I get
a selection I'd traverse my list of radio-button gadgets,
and remove the SELECTED flag if one of the gadgets were already
selected.  I'd also prefer to use RELVERIFY with these boolean
gadgets.

My question concerns the section on Mutual Exclusion of gadgets
in the 1.3 Libs+Devs RKM.  The RKM says that you must use
hit-select rather than toggle-select, and GADGIMMEDIATE
rather than RELVERIFY when doing mutual exclusion with
boolean gadgets.  However, earlier they talk about "turning
off" excluded gadgets; I'm never turning any of these gadgets
off (assuming this means the GADGDISABLE flag or OffGadget()),
just modifying the SELECTED state (and refreshing).  Is my
radio-button scenario described above considered "mutual
exclusion" as discussed in the RKM?  Is my plan ok, or am I
asking for trouble?  I'm new at this, so all help is appreciated,
and pointers to other sections in the RKM's are welcome.

Thanks,

Brian

-- 
Brian Smithey / SAIC, Geophysics Division / San Diego CA
uucp:	   uunet!seismo!esosun!smithey
Internet:  smithey@esosun.css.gov