Path: utzoo!attcan!uunet!wugate!wuarchive!brutus.cs.uiuc.edu!tut.cis.ohio-state.edu!bloom-beacon!EXPO.LCS.MIT.EDU!jim
From: jim@EXPO.LCS.MIT.EDU (Jim Fulton)
Newsgroups: comp.windows.x
Subject: Re: Problem with CvtStringToCursor?
Message-ID: <8907280305.AA15291@expo.lcs.mit.edu>
Date: 28 Jul 89 03:05:03 GMT
References: <1226@quintus.UUCP>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: X Consortium, MIT Laboratory for Computer Science
Lines: 17


	I was just poking around in Converters.c, and saw in the code for
	CvtStringToCursor() a static table of <name,number,cursor> triples 
	which serves to cache the Cursor corresponding to a cursor name:

	...

	Won't this go badly wrong if your application is using multiple
	displays?

Yup.

This is one (of possibly several :-) known bugs with the MIT R3
implementation with respect to multiple-display Xt applications.  I've been
meaning to fix it for a while (I have code that uses the Xlib extension
mechanism to provide callbacks on display closing so that the converters can
flush their caches)....