Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

gluttimerfunc(3glut) [osx man page]

glutTimerFunc(3GLUT)						       GLUT						      glutTimerFunc(3GLUT)

glutTimerFunc - registers a timer callback to be triggered in a specified number of milliseconds. SYNTAX
#include <GLUT/glut.h> void glutTimerFunc(unsigned int msecs, void (*func)(int value), value); ARGUMENTS
msecs Number of milliseconds to pass before calling the callback. func The timer callback function. value Integer value to pass to the timer callback. DESCRIPTION
glutTimerFunc registers the timer callback func to be triggered in at least msecs milliseconds. The value parameter to the timer callback will be the value of the value parameter to glutTimerFunc. Multiple timer callbacks at same or differing times may be registered simultane- ously. The number of milliseconds is a lower bound on the time before the callback is generated. GLUT attempts to deliver the timer callback as soon as possible after the expiration of the callback's time interval. There is no support for canceling a registered callback. Instead, ignore a callback based on its value parameter when it is triggered. SEE ALSO
glutIdleFunc AUTHOR
Mark J. Kilgard ( GLUT
3.7 glutTimerFunc(3GLUT)

Check Out this Related Man Page

glutIdleFunc(3GLUT)						       GLUT						       glutIdleFunc(3GLUT)

glutIdleFunc - sets the global idle callback. SYNTAX
void glutIdleFunc(void (*func)(void)); ARGUMENTS
func The new idle callback function. DESCRIPTION
glutIdleFunc sets the global idle callback to be func so a GLUT program can perform background processing tasks or continuous animation when window system events are not being received. If enabled, the idle callback is continuously called when events are not being received. The callback routine has no parameters. The current window and current menu will not be changed before the idle callback. Programs with multiple windows and/or menus should explicitly set the current window and/or current menu and not rely on its current setting. The amount of computation and rendering done in an idle callback should be minimized to avoid affecting the program's interactive response. In general, not more than a single frame of rendering should be done in an idle callback. Passing NULL to glutIdleFunc disables the generation of the idle callback. EXAMPLE
A typical idle callback to animate a window might look like: void idle(void) { time += 0.05; glutSetWindow(window); glutPostRedisplay(); } Notice how the idle callback does not do any actual drawing; it only advances the time scene state global variable. That is left to the window's display callback which will be triggered by the call to glutPostRedisplay. If you use the idle callback for animation, you should be sure to stop rendering when the window is not visible. This is easy to set up with a visibility callback. For example: void visible(int vis) { if (vis == GLUT_VISIBLE) glutIdleFunc(idle); else glutIdleFunc(NULL); } If you do use the idle callback for animation, one thing you should not do is setup the idle callback before calling glutMainLoop. It is much better to use the visibility callback to install idle callback when the window first becomes visible on the screen. SEE ALSO
glutTimerFunc, glutVisibilityFunc AUTHOR
Mark J. Kilgard ( GLUT
3.7 glutIdleFunc(3GLUT)
Man Page

Featured Tech Videos