Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ames!lll-tis!ptsfa!ihnp4!inuxc!iuvax!pur-ee!uiucdcs!uxc.cso.uiuc.edu!uicsrd!gaur
From: gaur@uicsrd.csrd.uiuc.edu
Newsgroups: comp.windows.x
Subject: XrEditors in the Xr library.
Message-ID: <5200005@uicsrd>
Date: Fri, 7-Aug-87 10:28:00 EDT
Article-I.D.: uicsrd.5200005
Posted: Fri Aug  7 10:28:00 1987
Date-Received: Sun, 9-Aug-87 22:02:19 EDT
Lines: 24
Nf-ID: #N:uicsrd:5200005:000:1203
Nf-From: uicsrd.csrd.uiuc.edu!gaur    Aug  7 09:28:00 1987


Hi! 
	I have a general question about the editors in the Xrlibrary.  We are running version X10.4. 
	I find that the region in which the editors (like TitleBar Editor, 
Scroll Bar Editor etc..) are drawn (inside a window) can be over written
by any bitmap manipulation (for Instance just doing an XText call in the window)
routines.
	Applications  which rely on X to truncate the output are then forced 
to not to overwrite on those regions or to redraw the editor instance . In any 
case they are forced to make such checks.
	A way to get around is to have a child window in the region where
the editor instance is drawn. So bitmap manipulation routines do not need to
make any checks to avoid corrupting  the editor instance.
	I feel the editors( at least the Title Bar and The Scroll Bar editors)
would be more usable if the editor instances could not be botched up by calls
like XText. For most of the time when a editor is drawn in a region I don't 
expect many application purposely overwriting in that region. 
	Are any later X versions going to or have addressed  this problem?
I would be thankful if somebody could give some information on this.

Thanks,
yogesh gaur

gaur%uicsrd@a.cs.uiuc.edu