glutmainloop(3) [centos man page]

UNTITLED
							       LOCAL								  UNTITLED

NAME

     glutMainLoop -- The standard GLUT event loop entry point.

LIBRARY

     OpenGLUT - mainloop

SYNOPSIS

     #include <openglut.h>

     void
     glutMainLoop(void);

DESCRIPTION

     This is the main driving force for an event-driven OpenGLUT program.  It alternates between calling glutMainLoopEvent() to process pending
     events and then either sleeping or calling your idle function (see glutIdleFunc()).

     This function  can   return, but GLUT's version of this function never returned.  And you must do special things to OpenGLUT to cause OpenG-
     LUT's version to return.

     The cross-reference section for this function's documentation should ideally contain every callback, but the list would be tediously long and
     prone to omissions.

CAVEATS

     For OpenGLUT developers' internal documentation: Runs until the  ExecState  changes to  GLUT_EXEC_STATE_STOP.

BUGS

     Talking to other message systems (e.g., network layers) can be a bit bothersome under the GLUT event model.

SEE ALSO

     glutMainLoopEvent(3) glutLeaveMainLoop(3) glutIdleFunc(3)

								       Epoch

UNTITLED
							       LOCAL								  UNTITLED

NAME

     glutCreateWindow -- Create a new top-level window

LIBRARY

     OpenGLUT - window

SYNOPSIS

     #include <openglut.h>

     int
     glutCreateWindow(const char* title);

PARAMETERS

      title	  Title for created window

DESCRIPTION

     This function sends a request for a window to be constructed.  OpenGLUT immediately constructs a data structure to track further events with
     the window, on the theory that eventually the window manager will get back to us with a real window.  This allows us to begin registering
     callbacks immediately.

     In fact, you  must   register a display callback via glutDisplayFunc() before you enter glutMainLoop().

     For onscreen windows, you should not depend upon the window concretely existing or being visibile until you are told that it exists and is
     visible via a registered callback.

     The return value is an  int.    It should be positive for valid windows or 0 if failure occurred for some reason (Though traditional GLUT
     tends to bail out and abort rather than returning errors.)  The integer is your  window id  .  Old GLUT promises that these integers are
     ``small''; we do not reuse old  id  s, but do produce them sequentially.

     You can change the title later via glutSetWindowTitle().

SEE ALSO

     glutDestroyWindow(3) glutCreateSubWindow(3) glutSetWindowTitle(3) glutCreateMenuWindow(3)

								       Epoch