🚀 go-pugleaf

In article <16305@gryphon.COM> rickf@pnet02.cts.com (Rick Flower) writes:
>I posted a message earlier in the week asking about Mutual Exclusion of
>Boolean Gadgets, and I have received several letters from other users out
>there (thank guys, for the input!!).  Most of those people didn't or couldn't
>make this "mutual exclusion of gadgets" work.. I know that the old RKM's say
>that this field in the Gadget structure is ignored, but according to the
>Workbench 1.3 Assembly Include headers, it makes it sound as if this feature
>is now working in 1.3!  I'm basically asking if this is the case, and if so,
>how the heck can I get it to work??

Intuition does not provide for mutual exclusion of boolean gadgets.  Intuition
was basically unchanged for V1.3.  Thus the same rules apply for V1.3 as were
in effect for V1.2.  The V1.2 Enhancer Manual offers a method of managing
mutually-excluded gadgets yourself.  Briefly, remove the boolean gadget
from the window/requester [RemoveGadget() or RemoveGList()], set or clear
(as necessary) the gadget's SELECTED flag,  add the gadget back to the
window/requester [AddGadget() or AddGList()], and, finally, refresh
[RefreshGadgets() or RefreshGList()].

A warning from the Enhancer:

    It is strongly recommended that you play these games only with Boolean
    gadgets rendered with images and highlighted by complement mode rendering.
    Further, the Activation Type should be GADGIMMEDIATE (and not RELVERIFY,
    nor TOGGLESELECT) with your state changes executed upon receiving the
    GADGETDOWN message.

-- 
Eric Cotton
Commodore-Amiga                                               (215) 431-9100
1200 Wilson Drive                        {uunet|pyramid|rutgers}!cbmvax!eric
West Chester, PA 19380            "I don't find this stuff amusing anymore."