CMX11 Version 1.6 
		Bug Update Report for October 1993
	   For Connection Machine CM-5 Systems

FIXED BUGS

The following bugs have been fixed in the current release,
Version 1.6. For a description of any bug listed here, contact
your Applications Engineer or the Customer Support group
at Thinking Machines Corporation.

TMCaa04222	Wrong visual returned for 24-bit TrueColor windows
TMCaa04199	mouse.h doesn't compile under non-ANSI C

OUTSTANDING BUGS

The following bugs are outstanding in the current release.

TMCaa04117	string & polygon funcs only support 1-d shapes in C*


Each of these bugs is detailed below.

*********************************************************
ID: TMCaa04117

Title:	string & polygon funcs only support 1-d shapes in C*


Description:
 In the C* CMX11 interface, CMXDrawString, CMXDrawCString, CMXFillPolygon
and CMXFillCPolygon only correctly support 1-d shapes.  Shapes of greater
rank will produce the following runtime error:
   CMX11 error in CMXDrawCString: string must have rank 1 greater than
   color: actual X rank is 2, and color rank is 2.
  
  

Workaround:
Only use 1-d shapes for X, Y and string (or polygon).
  

Status:	Outstanding.

*********************************************************
ID: TMCaa04199

Title:	mouse.h doesn't compile under non-ANSI C


Description:
 cm/mouse.h contains unprotected ANSI prototypes for all
the functions it declares.  This causes it to be uncompilable with a
standard (non-ANSI) C compiler.
  

Workaround:
Don't include it, or #define __MOUSE_H before including it (which will
cause the contents to be ignored).
  

Status:	Fixed in 1.6.

*********************************************************
ID: TMCaa04222

Title:	Wrong visual returned for 24-bit TrueColor windows


Description:
 Passing a large value of ncolors and DirectColor or TrueColor to
CMXCreateDisplayClass triggers a bug which causes an incorrect visual (of
the correct class, but often the wrong depth) to be returned.
  

Workaround:
Don't use the 'ncolors' argument to CMXCreateDisplayClass; it will always
choose a 24-bit visual for a DirectColor or TrueColor visual class if one's
available.
  

Status:	Fixed in 1.6.