Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

unregister_callback(9r) [osf1 man page]

unregister_callback(9r) 												   unregister_callback(9r)

NAME
unregister_callback - General: Deregisters a configuration callback routine SYNOPSIS
int unregister_callback( void (*function) (), int point, int order, ulong argument ); ARGUMENTS
Specifies the name of the routine that you want to deregister. You must have previously registered this callback routine by calling regis- ter_callback. Specifies the execution point at which the kernel calls the callback routine previously registered by calling register_call- back. The execution point you pass to this argument must match the value you passed to the point argument in the call to register_callback. Specifies the order value that you specified in a previous call to register_callback. Specifies an argument that you want the kernel to pass to the callback routine that you previously registered by calling register_callback. The argument you pass to this argument must match the value you passed to argument in the call to register_callback. You would pass the integer constant 0L if you passed this in the previ- ous call to register_callback to indicate there is no argument. DESCRIPTION
The unregister_callback routine deregisters a kernel module's configuration callback routine. The kernel module previously registered its routine or routines by calling the register_callback routine. The values you pass to unregister_callback must be the same ones you previ- ously passed to register_callback to deregister a specific routine. Kernel modules call unregister_callback to deregister the callback rou- tine when it is no longer needed. A kernel module typically calls unregister_callback when it encounters a fatal error during static or dynamic configuration. The cfgmgr framework executes callback routines scheduled to run after single-user mode each time the system goes from multiuser mode to single-user mode and back to multiuser mode. You should unregister any callback routines if you do not want this to occur. NOTES
The kernel maintains an internal callback list that stores the values you pass to the register_callback routine. These callbacks remain registered until the user removes them. The unregister_callback routine searches through the callback list for the specified callback routine, the specified point, the specified order, and the specified argument and removes that routine from the list. RETURN VALUES
Upon successful completion, the unregister_callback routine returns the value ESUCCESS. Otherwise, unregister_callback returns the following error constant, defined in /usr/sys/include/sys/errno.h: The value you passed to the point argument is outside the minimum and maximum range. The callback you specified to be removed does not exist in the callback list. The callback you specified to be removed does not exist in the callback list. FILES
SEE ALSO
Routines: register_callback(9r) unregister_callback(9r)

Check Out this Related Man Page

glutDisplayFunc(3GLUT)						       GLUT						    glutDisplayFunc(3GLUT)

NAME
glutDisplayFunc - sets the display callback for the current window. SYNTAX
#include <GLUT/glut.h> void glutDisplayFunc(void (*func)(void)); ARGUMENTS
func The new display callback function. DESCRIPTION
glutDisplayFunc sets the display callback for the current window. When GLUT determines that the normal plane for the window needs to be redisplayed, the display callback for the window is called. Before the callback, the current window is set to the window needing to be redisplayed and (if no overlay display callback is registered) the layer in use is set to the normal plane. The display callback is called with no parameters. The entire normal plane region should be redisplayed in response to the callback (this includes ancillary buffers if your program depends on their state). GLUT determines when the display callback should be triggered based on the window's redisplay state. The redisplay state for a window can be either set explicitly by calling glutPostRedisplay or implicitly as the result of window damage reported by the window system. Multiple posted redisplays for a window are coalesced by GLUT to minimize the number of display callbacks called. When an overlay is established for a window, but there is no overlay display callback registered, the display callback is used for redis- playing both the overlay and normal plane (that is, it will be called if either the redisplay state or overlay redisplay state is set). In this case, the layer in use is not implicitly changed on entry to the display callback. See glutOverlayDisplayFunc to understand how distinct callbacks for the overlay and normal plane of a window may be established. When a window is created, no display callback exists for the window. It is the responsibility of the programmer to install a display call- back for the window before the window is shown. A display callback must be registered for any window that is shown. If a window becomes displayed without a display callback being registered, a fatal error occurs. Passing NULL to glutDisplayFunc is illegal as of GLUT 3.0; there is no way to ``deregister'' a display callback (though another callback routine can always be registered). Upon return from the display callback, the normal damaged state of the window (returned by calling glutLayerGet(GLUT_NORMAL_DAMAGED) is cleared. If there is no overlay display callback registered the overlay damaged state of the window (returned by calling glutLayer- Get(GLUT_OVERLAY_DAMAGED) is also cleared. SEE ALSO
glutCreateMenu, glutPostRedisplay, glutOverlayDisplayFunc AUTHOR
Mark J. Kilgard (mjk@nvidia.com) GLUT
3.7 glutDisplayFunc(3GLUT)
Man Page