Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!tut.cis.ohio-state.edu!ucsd!hub!doug
From: doug@voodoo.ucsb.edu
Newsgroups: comp.sys.amiga.tech
Subject: Re: Mutual Exclude Gadgets
Message-ID: <3454@hub.UUCP>
Date: 3 Jan 90 04:46:27 GMT
Sender: news@hub.UUCP
Organization: UC, Santa Barbara. Physics Computer Services
Lines: 27

-Message-Text-Follows-
In article <899@tardis.Tymnet.COM>, jms@tardis.Tymnet.COM (Joe Smith) writes...
>After reading the follow-up postings and email from Henry, I am still missing
>something.  In the example above, who decides that bit 2 is available for use
>by gadget A?  If it's decided by the programmer at compile time, then the
>code won't work if bit 2 is one of the bits assigned to a system gadget.
>(It will exclude the system gadget when that was not what is desired.)
>If it's determined at run time, then how is this information passed back to
>the program?  I like the idea, but how is it implemented?

There are currently no system gadgets which use or need mutual exclusion
Mutual exclusion would be local to a window so only the window gadgets
matter as system gadgets in this discusion. System gadgets just wouldn't
have any bits set. In the future, someone may actualy come up with some
system gadgets which need to use mutual exclusion, but this could be
handled by either alocating system mutual exclude bits from the top, 
and user bits from the bottom (liest significant), or by adding a new
ulong for system mutual exclude bits. 

Most likely it will be the users responsibility to choose the bits to
use.

The only thing I don't like about this solution, is that it requires
searching the entire list of gadgets every time a gadget with a mutual
exclude bit set is selected.

Douglas Peale