		       Known bugs in SCIX v1.00

1.	Pulldown-menu.
	If the menu is opened (by a ButtonPress in the menu widget) and then
	the mouse-button is released in a window that selects ButtonRelease
	(like a button widget) then the menu won't get the ButtonRelease event
	and hence the the menu will stay open in spite of the fact that the
	mouse button has been released. This is fixable (of course), but I'm
	not sure of the best way to do it.

2.	StringEditor.
	It is possible to enter a string that is much longer than the widget
	that it is written in.

3.	Scrollbar.
	Usually the scrollbar ensures that it gets MotionNotify events when
	the cursor is moved with a mouse button pressed even if the cursor
	leaves the scrollbar's window. This is done with a so-called
	passive grab on the mouse buttons an works perfectly with most X
	servers. Not, hwoever, with the purportedly X11R4 based X server in
	an Tandberg X terminal available to us. We have no clue yet.

4.	Widgets don't support stretching and shrinking (yet).

5.	The Battleships demo breaks on a DECstation 3100 running X11R4
	when a QueryTextExtents recieves an ALLOC error. This is very
	strange as other QueryTextExtens work ok. But it works on Sparcs
	running X11R4 and DECstations running a DECwindows server. Probably
	the bug is in SCIX, but we're a little confused about what it
	might be.

6. 	Requests that generate long replies are painstakingly slow. An example
	of such a request is GetImage with a large area.

7.	The request GetMotionEvents previously crashed the server. Now it
	seems to work, but we haven't been able to test it extensively,
	since none of the servers we have access to retain a motion buffer.

8.	Currently there is no support for the parameter 'All to CreateColormap
	(to allocate all pixels writable).

9.	If one examines the so called initial reply (accessible through the
	message 'scix-initial-reply to the display object) it is necessary
	to be aware that this data is recieved before the disassembler is
	fully activated. Therefore some data therein isn't represented as
	objects. This shouldn't affect normal usage, since the important
	data is accessible through methods to the screen object.

10.	SendEvent isn't fully supported, the assembling of the event has
	to be done by hand.
