[openglean-devel]What to expect in the next release.

[Richard R. <sf...@ol...>]

At this point, the upcoming release is mostly a maint. release:

 * I see that freeglut has picked up the OpenGLEAN use of a macro to
   define the string-to-function-pointer translation in ext.c.
   OpenGLEAN did this only to ensure that the string names matched
   the symbol names (ensuring that the symbol name and the string
   were exact matches such that a typo in the string name would
   cause a compile-time error).  I held back previously from
   building the table at run-time, but now will probably do so.
   The reason to do so is to work around a bug in MinGW in the
   creation of WIN32 ".dll" shared libraries.  I don't know if
   the bug is somewhat inherent in the PECOFF spec, but MSVC
   never had a problem with the code.  I held off doing this obvious
   workaround because it is still (IMHO) a compiler bug, and it was
   not certain that the workaround would actually *work* *around*
   the compiler bug.

   I don't actually have MinGW set up, so thanks to the freeglut
   people for testing this.  (They will probably include this fix
   in their release, set to occur sometime perhaps in early June.)

 * A minor bug in the wheel event "button-up" event on WIN32 is
   corrected.

 * Found and closed a memory leak in X TextProperty handling.

 * Generally improved documentation.

 * Added the "cuboctohedron" that John Fay promotes (so much so
   that he has also snuck an implementation into the freeglut
   "shapes" demo, though the demo is supposed to be demonstrating
   the library shapes, and freeglut does not include the cuboctohedron
   shape).

 * Code cleanup for the demos.

 * Improved clock granularity.  Maybe.

 * Minor ensurance of glReadBuffer()/glDrawBuffer() invocation at
   window creation (not sure if this really matters).


The short summary is: More bug fixes, more documentation refinements,
and a new solid/wire shape.

--=20
  "I probably don't know what I'm talking about."  http://www.olib.org/~rkr/