Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!think.com!snorkelwacker.mit.edu!bloom-beacon!LARRY.MCRCIM.MCGILL.EDU!mouse
From: mouse@LARRY.MCRCIM.MCGILL.EDU
Newsgroups: comp.windows.x
Subject: Re:  Using XDefineCursor properly....
Message-ID: <9011270039.AA23832@Larry.McRCIM.McGill.EDU>
Date: 27 Nov 90 00:39:19 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 19

> During the course of a cpu intensive callback, I want to change the
> mouse pointer to XC_watch while it is in my app.

> Do I have to call XDefineCursor for every widget the pointer may
> travel through?

No.  The simple solution is to create an InputOnly window which covers
your top-level window.  Give this window the cursor you want.  Then
when you want to use this cursor, map and raise this window; to go back
to normal, unmap it.  This will automatically keep you from getting
mouse events - or rather, mouse events will be generated on this window
instead of the window they "visually" belong to.  Depending on
precisely how the window manager works, it may or may not have a
similar effect on keystrokes as well.

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu