Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!ll-xn!mit-eddie!bbn!rochester!cornell!batcomputer!hsgj
From: hsgj@batcomputer.tn.cornell.edu (Dan Green)
Newsgroups: comp.sys.amiga.tech
Subject: Re: IDCMP ports
Message-ID: <4540@batcomputer.tn.cornell.edu>
Date: 23 Apr 88 07:12:53 GMT
References: <2336@mit-amt.MEDIA.MIT.EDU> <353@ardent.UUCP>
Reply-To: hsgj@tcgould.tn.cornell.edu (Dan Green)
Distribution: na
Organization: Cornell Theory Center, Cornell University, Ithaca NY
Lines: 28
Keywords: screens windows

In article <> (Rob Peck) writes:
>In article <> (Darren L. Leigh) writes:
>> If I have an application that has created a custom screen and I don't
>> want to open any windows, how do I get an IDCMP port between me and
>> Intuition?  > information without cluttering up the world with windows.
>
>Someone suggested the tiny-window 1x1 pixel as ushow uses, but that won't
>do what you wish.  Problem is:  if you click in the custom screen, the
>tinywindow is no longer the active one, and its IDCMP won't see much
>if any input.  Appropriate solution is to open ONE window, covering the
>entire custom screen (except perhaps the screen title bar area perhaps).

An additional point is that you can use a 1x1 pixel window, but make
sure you set the flag (forget the name) that notifies you when you
are no longer  the active window.  I think its (INACTIVE_WINDOW) or
something like that.  Anyways, when you get that message, it means the
user clicked on the screen.  With the message is the mouse X,Y, in case
you need that info.  So then you do an Activate() call to make your
window active again so you can get more IDCMP input.

Please note that everyone will chastize you if you do this sort of
behavior on a screen where windows from other programs exist!  Thus
you can only do this on your own custom screen, which I gather was
the original intent.

-- Dan Green
-- 
ARPA:  hsgj@tcgould.tn.cornell.edu
UUCP:  ihnp4!cornell!batcomputer!hsgj   BITNET:  hsgj@cornella