From: Jocelyn F. <joc...@la...> - 2008-06-27 16:39:24
|
While trying to figure out what should be added to the documentation, I cannot see any difference between the GLUT_ACTION_CONTINUE_EXECUTION and GLUT_ACTION_GLUTMAINLOOP_RETURNS values of the GLUT_ACTION_ON_WINDOW_CLOSE option. Both lead to a call to fgDeinitialize() and the exit of the main loop. The only thing I can see is in the Win32 fgWindowProc function: PostQuitMessage() may be called or not. But I guess this not makes a big difference. Does this mean GLUT_ACTION_CONTINUE_EXECUTION is now deprecated, since it does not make freeglut stay in the main loop, or am I missing something? Other topic: what is the purpose of the GLUT_INIT_* options? They are redundant with the glutInit* functions, except that you cannot call glutSetOption() before calling glutInit(). -- Jocelyn Fréchot |
From: Fay J. F Dr C. U. 46 S. <joh...@eg...> - 2008-06-27 16:59:08
|
To answer the "GLUT_ACTION" question, the question at hand is what happens when the user closes a window by clicking on the "X" in the upper right hand corner. "Continue execution" is supposed to stay in the main loop; "main loop returns" is supposed to return control to the calling program. The default behavior--which is what GLUT does--is to stop executing the program immediately. John F. Fay Technical Fellow Jacobs Technology TEAS Group 850-883-1294 -----Original Message----- From: fre...@li... [mailto:fre...@li...] On Behalf Of Jocelyn Fréchot Sent: Friday, June 27, 2008 11:39 AM To: FreeGLUT developers list Subject: [Freeglut-developer] About options While trying to figure out what should be added to the documentation, I cannot see any difference between the GLUT_ACTION_CONTINUE_EXECUTION and GLUT_ACTION_GLUTMAINLOOP_RETURNS values of the GLUT_ACTION_ON_WINDOW_CLOSE option. Both lead to a call to fgDeinitialize() and the exit of the main loop. The only thing I can see is in the Win32 fgWindowProc function: PostQuitMessage() may be called or not. But I guess this not makes a big difference. Does this mean GLUT_ACTION_CONTINUE_EXECUTION is now deprecated, since it does not make freeglut stay in the main loop, or am I missing something? Other topic: what is the purpose of the GLUT_INIT_* options? They are redundant with the glutInit* functions, except that you cannot call glutSetOption() before calling glutInit(). -- Jocelyn Fréchot ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Freeglut-developer mailing list Fre...@li... https://lists.sourceforge.net/lists/listinfo/freeglut-developer |
From: Jocelyn F. <joc...@la...> - 2008-06-29 13:57:46
|
Jocelyn Fréchot wrote: > I cannot see any difference between the GLUT_ACTION_CONTINUE_EXECUTION > and GLUT_ACTION_GLUTMAINLOOP_RETURNS values of the > GLUT_ACTION_ON_WINDOW_CLOSE option. Both lead to a call to > fgDeinitialize() and the exit of the main loop. False alarm: the “continue execution” action makes sense (and works as expected) when there is more than one window. -- Jocelyn Fréchot |