Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!bagate!cbmvax!peter
From: peter@cbmvax.commodore.com (Peter Cherna)
Newsgroups: comp.sys.amiga.programmer,adsp.sw
Subject: Re: "Busy" pointer
Keywords: Busy pointer, new function suggestion
Message-ID: <22780@cbmvax.commodore.com>
Date: 28 Jun 91 15:55:49 GMT
References: <1991Jun26.030833.9974@crash.cts.com> <22702@cbmvax.commodore.com> <1991Jun27.164849.3171@ifi.unizh.ch>
Reply-To: peter@cbmvax.commodore.com (Peter Cherna)
Organization: Commodore-Amiga, Inc.  West Chester, PA.
Lines: 23

In article <1991Jun27.164849.3171@ifi.unizh.ch> matija@amiga.ifi.unizh.ch (Matija Milostnik) writes:

>This is my suggestion 
>Add in intuition two new functions. 
>- SetBusyPointer(Window,Mask)
>  Mask would be a mask of desired IDCMP mesagges the user want to hear.
>  Intuition would AND the incoming messagaes with Mask and if the result
>  is NOT zero forword it to the window, else it would ReplyMsg.
>- ClearBusyPointer(Window) 
>  Bussinse as usual.

Intuition already provides ModifyIDCMP() which the application can use
to choke off some or all classes of message.  There is no good reason
to combine that into SetBusyPointer().

> Matija

     Peter
--
Peter Cherna, Operating Systems Development Group, Commodore-Amiga, Inc.
{uunet|rutgers}!cbmvax!peter    peter@cbmvax.commodore.com
My opinions do not necessarily represent the opinions of my employer.
"Gosh, didn't he have anything positive to say at all?"