Path: utzoo!mnetor!uunet!lll-winken!lll-tis!oodis01!uplherc!utah-gr!utah-cs!thomson
From: thomson@utah-cs.UUCP (Richard A Thomson)
Newsgroups: comp.sys.amiga.tech
Subject: Re: IDCMP ports
Message-ID: <5429@utah-cs.UUCP>
Date: 21 Apr 88 06:34:56 GMT
References: <2336@mit-amt.MEDIA.MIT.EDU>
Reply-To: thomson@cs.utah.edu.UUCP (Richard A Thomson)
Distribution: na
Organization: University of Utah CS Dept
Lines: 27
Keywords: screens windows

In article <2336@mit-amt.MEDIA.MIT.EDU> dlleigh@media-lab.UUCP
	(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?  All the documentation talks about windows and I don't see
>a way to do it otherwise.  I just want some mouse moves and gadget
>information without cluttering up the world with windows.

My best guess is that you should open a BORDERLESS BACKDROP window.  For
all intents and purposes, this would appear like a blank screen to the
user, but you could attach an IDCMP port to it to receive mouse events.
It also has the advantage that if you render into the RastPort of the
window, and not the screen, then any title bar and system gadget refreshes
for the screen won't trash your rendered graphics.  It also allows you
to attach a 'menu' to a screen.  (It's actually attached to the borderless,
backdrop window but the user sees only the screen)

>Is this possible?  If not, is this why I see gratuitous tiny windows
>behind so many applications?

Perhaps these gratuitous tiny windows are the result of poor programming?

> Darren Leigh			dlleigh@media-lab.mit.edu

						-- Rich
-- 
Richard Thomson		3190 MEB, University of Utah, Salt Lake City, UT 84112
thomson@cs.utah.edu	(801) 584-4555: Talk to a machine, they're lonely.