Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!ames!oliveb!amiga!cbmvax!jesup
From: jesup@cbmvax.UUCP (Randell Jesup)
Newsgroups: comp.sys.amiga.tech
Subject: Re: inputs from many windows
Message-ID: <5864@cbmvax.UUCP>
Date: 31 Jan 89 20:42:43 GMT
References: <3778@crash.cts.com> <2509@kalliope.rice.edu>
Reply-To: jesup@cbmvax.UUCP (Randell Jesup)
Organization: Commodore Technology, West Chester, PA
Lines: 20

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.

	Actually less, since a number of signals (like ^C-F, plus others)
are pre-allocated to the system.

>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, signal allocations are on a per-task basis.

-- 
Randell Jesup, Commodore Engineering {uunet|rutgers|allegra}!cbmvax!jesup