GLUT_BORDERLESS seems to vary by the window manager on X11, though twm (for example) performs very similarly to WIN32. But KDE's window manager (for example) does not let you send keystrokes to borderless windows without OpenGLEAN hacks.
Mice are optional, but OpenGLEAN is only able to check for them under WIN32.
Mice can have a varying number of buttons, but OpenGLEAN assumes exactly 3 on UNIX_X11.
HAS/OWNS queries on joysticks don't report how many joysticks are there.
BUTTONS/AXES queres on joysticks only work with the first joystick found.
Only supports querying for one joystick.
Replacing game mode with a better design was discussed at some length in early 2004.
One idea was to decompose gamemode into component parts and implement them separately, where each part then either succeeds totally or fails totally:
There is no way for game mode to report a partial failure.
There is no way to guarantee cleanup if OpenGLEAN crashes during game mode---or if the client crashes or directly exits, etc.
Some XFree86 releases, with some drivers, can fail to set the video mode properly, resulting in disasterous failure (an unusable display). This is presently somewhat headed off by a compile-time option, but a runtime option would be better, as there may be cases where the user is willing to put up with the risk for some---and only some---OpenGLEAN applications. Since game mode applications are somewhat dim-witted about such user preferences, it seems, an OpenGLEAN runtime control could be desirable.
Supported in part by SourceForge.net.
Generated on Fri Sep 16 20:15:32 2005 for OpenGLEAN by
doxygen 1.4.3
The OpenGLEAN project is hosted by
olib.org and
SourceForge.