glutInit man page
glutInit — Initialize OpenGLUT data structures.
OpenGLUT - mainloop
glutInit(int *pargc, char **argv);
Pointer to something like main()'s
Something like main()'s
This function should be called once, near the start of any GLUT, freeglut, or OpenGLUT program. It serves two vital roles:
- It allows OpenGLUT to initialize internal structures.
- It allows OpenGLUT to process command-line arguments to control the initial window position, etc.
You should take note of the interaction between glutInit() and the related functions such as glutInitWindowPosition(). OpenGLUT always uses the most recent configuration information, so if you call glutInit(), then glutInitWindowPosition(), you prevent the user from controlling the initial window position via a command-line parameter.
glutInit() will remove from
any parameters that it recognizes in the command line. The following command-line parameters are suported:
Insist on only OpenGL direct rendering. Direct rendering is normally requested but indirect is normally accepted.
is not always available. See
Attempt only indirect OpenGL rendering.
is always available. See
Open the window in iconized form.
Print any detected OpenGL errors via glutReportErrors(). Presently done at the bottom of glutMainLoopEvent().
Synchronize the window system communications heavily.
Additionally, this function checks whether the environment variable
is defined (only on UNIX_X11); if so, OpenGLUT will periodically print the average number of times per second that your program calls glutSwapBuffers().
You really should always call this, even if you are a WIN32 user. It provides a way for the user to directly inform OpenGLUT about preferences without the application needing to explicitly deal with those issues. This is also where OpenGLUT retrieves your program's name to help disambiguate error and warning messages it may be forced to emit.
sets a flag, but is not actually used at this time.
Lots of code does XFlush() on the X server, regardless of whether
is specified. Much of that appears to be required in order to support direct client invocation of glutMainLoopEvent(), regrettably. However, if one calls glutMainLoop(), instead, we might avoid gratuitous XFlush() calls. (That last sentence isn't particularly germain to this function, but there's no better place to make this remark at this time.) Even for glutMainLoopEvent(), we may be able to coalesce many XFlush() calls.
glutInitWindowPosition(3) glutInitWindowSize(3) glutInitDisplayMode(3) glutInitDisplayString(3) glutCreateWindow(3) glutDisplayFunc(3) glutMainLoop(3) glutMainLoopEvent(3) glutReportErrors(3) glutSwapBuffers(3)
glutFullScreen(3), glutInitDisplayMode(3), glutInitDisplayString(3), glutInitWindowPosition(3), glutInitWindowSize(3), glutPositionWindow(3), glutReportErrors(3), glutReshapeWindow(3), glutSetOption(3).