Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cwjcc!hal!nic.MR.NET!umn-d-ub!uwvax!astroatc!nicmad!madnix!aaron
From: aaron@madnix.UUCP (Aaron Avery)
Newsgroups: comp.sys.amiga.tech
Subject: Re: inputs from many windows
Message-ID: <454@madnix.UUCP>
Date: 1 Feb 89 13:48:16 GMT
References: <3778@crash.cts.com> <2509@kalliope.rice.edu>
Reply-To: aaron@madnix.UUCP (Aaron Avery)
Organization: ASDG Incorporated
Lines: 25

In article <2509@kalliope.rice.edu> phil@Rice.edu (William LeFebvre) writes:
)This is my thinking (and it might be wrong---I'm not sure).  Separate
)IDCMPs means separate message ports.  Separate ports means separate signal
)bits.  And you can only have 32 sigbits, right (only 32 bits in a long)?
)That would imply to me that you can have, at the most, 32 open windows in
)your task, if you use a separate IDCMP for each window.

That's my impression of what the problem is. Also, it's worse than that. The
system pre-allocates 16 sigbits for you, so you only have 16 more to allocate
yourself.
 
)This leads to something for which I don't know the answer:  are sigbits
)allocated on a per-task basis or do they need to be unique throughout the
)entire system?  In other words, can two separate tasks both be using the
)same signal bit for two separate ports?  Seems to me that it would just be
)too restrictive if they couldn't.

Yes, they're on a per-task basis. 32 signals for the whole system would be a
TAD restrictive!-)

-- 
Aaron Avery, ASDG Inc.         "A mime is a terrible thing to waste."
                                                             -- Robin Williams
ARPA: madnix!aaron@cs.wisc.edu   {uunet|ncoast}!marque!
UUCP:   {harvard|rutgers|ucbvax}!uwvax!astroatc!nicmad!madnix!aaron