Xref: utzoo comp.sys.mac.comm:3923 comp.sys.mac.system:6530
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!agate!stanford.edu!neon.Stanford.EDU!pescadero.Stanford.EDU!philip
From: philip@pescadero.Stanford.EDU (Philip Machanick)
Newsgroups: comp.sys.mac.comm,comp.sys.mac.system
Subject: MacX cursor bug?
Message-ID: <1991May29.211302.13170@neon.Stanford.EDU>
Date: 29 May 91 21:13:02 GMT
Sender: news@neon.Stanford.EDU (USENET News System)
Reply-To: philip@pescadero.stanford.edu
Organization: Stanford University
Lines: 26

If MacX is in the background, and the foreground program closes
a window, MacX changes the cursor if it happens to be over
a MacX window at the time. It took me a while to work this out,
because it only happens with applications that don't themselves
change the cursor when the window disappears, and when the cursor
is over the frontmost MacX window, which must also be an xterm
window.

To make it just that little bit more puzzling, I only seem to
get this behaviour with xterm windows.

Here's a repeateable way of getting this to happen:
o put an xterm window frontmost in MacX
o switch to the Finder and open a window
o position the cursor over the content region of the
  front xterm widow (without clicking), and type
  COMMAND-W to close the Finder window
The cursor changes to the cursor appropriate for the
xterm (text, or scroll bar double-arrow) for a few seconds.

All this is with System 7.0, and a IIcx. Can anyone else
reproduce this? I hope this is just a cosmetic bug, not a
symptom of deeper trouble.
-- 
Philip Machanick
philip@pescadero.stanford.edu