Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!titan!phil
From: phil@titan.rice.edu (William LeFebvre)
Newsgroups: comp.sys.amiga.tech
Subject: Re: inputs from many windows
Summary: Separate IDCMPs too restrictive?
Message-ID: <2509@kalliope.rice.edu>
Date: 30 Jan 89 17:53:27 GMT
References: <3778@crash.cts.com>
Sender: usenet@rice.edu
Reply-To: phil@Rice.edu (William LeFebvre)
Organization: Rice University, Houston
Lines: 22

In article <3778@crash.cts.com> billk@pnet01.cts.com (Bill W. Kelly) writes:
>What's the _probem_ with allowing these poor little windows to each have their
>own IDCMP's?  
>...
>Am I missing something?

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.

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.

			William LeFebvre
			Department of Computer Science
			Rice University
			<phil@Rice.edu>