Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!lll-winken!lll-tis!ames!mailrus!ulowell!masscomp!aat
From: aat@masscomp.UUCP (Andy Takats)
Newsgroups: comp.windows.x
Subject: Re: XDefineCursor with cursor = NONE
Message-ID: <317@masscomp.UUCP>
Date: 24 Oct 88 15:10:02 GMT
Article-I.D.: masscomp.317
References: <8810211634.AA11760@xpiinc.uu.net> <8810211915.AA17030@LYRE.MIT.EDU>
Reply-To: aat@masscomp.UUCP (Andy Takats)
Organization: MASSCOMP - Westford, Ma
Lines: 16

In article <8810211915.AA17030@LYRE.MIT.EDU> swick@ATHENA.MIT.EDU (Ralph R. Swick) writes:
>O'Reilly is wrong.  XUndefineCursor is equivalent to
^^^^^^^^^^^^^^^^^^
>XDefineCursor(cursor=None), both of which actually use the
>ChangeWindowAttributes request.  Setting the....

I'm not particularly fond of the O'Reilly manuals, but I don't think it's
fair to say something like this when the MIT C Library Reference manual
states (R2) for the XDefineCursor call:

	"....You can pass None if no cursor is to be displayed."

That sounds like more than just O'Reilly is wrong.


Andy Takats
..!{uunet,harvard}!masscomp!aat