Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!converse
From: converse@EXPO.LCS.MIT.EDU (Donna Converse)
Newsgroups: comp.windows.x
Subject: Re: InputOnly Curiosity
Message-ID: <9002091833.AA01183@expo.lcs.mit.edu>
Date: 9 Feb 90 18:33:50 GMT
References: <9002082029.AA03389@zurich.ai.mit.edu>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: X Consortium, MIT Laboratory for Computer Science
Lines: 23


> Does anyone have a concrete example of where you'd use an InputOnly
> window?

see Scheifler Gettys & Newman page 30:

	InputOnly windows are used for controlling input events in situations
	where InputOutput windows are unnecessary.  InputOnly windows are 
	invisible; can only be used to control such things as cursors, input 
	event generation, and grabbing; and coannot be used in any graphics
	requests.

At certain times, xmh maps an InputOnly window which does not propagate 
key and pointer events, preventing the user from sending events to xmh's
interface.  The window is intended to protect against the problem of the
user initiating a function multiple times because the the interface has a
slow response.  It is an economical way to temporarily ignore events.
The default cursor of this window looks like a wrist watch, which cues the
user to wait with the knowledge that something is indeed happening.


Donna Converse
converse@expo.lcs.mit.edu