This manual page is for Mac OS X version 10.6.3

If you are running a different version of Mac OS X, view the documentation locally:

  • In Terminal, using the man(1) command

Reading manual pages

Manual pages are intended as a quick reference for people who already understand a technology.

  • For more information about the manual page format, see the manual page for manpages(5).

  • For more information about this technology, look for other documentation in the Apple Reference Library.

  • For general information about writing shell scripts, read Shell Scripting Primer.



glutPostOverlayRedisplay(3GLUT)                     GLUT                     glutPostOverlayRedisplay(3GLUT)



NAME
       glutPostOverlayRedisplay, glutPostWindowOverlayRedisplay - marks the overlay of the current or speci-fied specified
       fied window as needing to be redisplayed.

SYNTAX
       void glutPostOverlayRedisplay(void);
       void glutPostWindowOverlayRedisplay(int win);

DESCRIPTION
       Mark the overlay of current window as needing to be redisplayed.  The next  iteration  through  glut-MainLoop, glutMainLoop,
       MainLoop, the window's overlay display callback (or simply the display callback if no overlay display
       callback is registered) will be called to redisplay the window's overlay  plane.  Multiple  calls  to
       glutPostOverlayRedisplay  before  the  next display callback opportunity (or overlay display callback
       opportunity if one is registered) generate only a single redisplay. glutPostOverlayRedisplay  may  be
       called within a window's display or overlay display callback to re-mark that window for redisplay.

       Logically,  overlay  damage notification for a window is treated as a glutPostOverlayRedisplay on the
       damaged window. Unlike damage reported by the window system, glutPostOverlayRedisplay will not set to
       true the overlay's damaged status (returned by glutLayerGet(GLUT_OVERLAY_DAMAGED).

       If the window you want to post an overlay redisplay on is not already current (and you do not require
       it to be immediately made current), using glutPostWindowOverlayRedisplay is more efficient that call-ing calling
       ing glutSetWindow to the desired window and then calling glutPostOverlayRedisplay.

EXAMPLE
       If you are doing an interactive effect like rubberbanding in the overlay, it is a good idea to struc-ture structure
       ture your rendering to minimize flicker (most overlays are single-buffered).  Only clear the  overlay
       if  you know that the window has been damaged.  Otherwise, try to simply erase what you last drew and
       redraw it in an updated position.  Here is an example overlay  display  callback  used  to  implement
       overlay rubberbanding:

         void
         redrawOverlay(void)
         {
           static int prevStretchX, prevStretchY;

           if (glutLayerGet(GLUT_OVERLAY_DAMAGED)) {
             /* Damage means we needwindoay callback 4at theeeeeeeeeeeeeeey displayOverlayRedisplay - marks the
       o6s w_COLOR_BUFFER_BITglutCrea} esteck 4at theeeeUnample.  Heay(voi-d)
       lay - marks thIativi(urrent windglutCreas thBlutns w_LINE_LOOPglutCreas thVesplx2ide chorXow tchorYglutCreas thVesplx2ide chorXowLAY_DAMAGED)glutCreas thVesplx2idrGet(GLUT_OVERLAY_DAMAGED)glutCreas thVesplx2idrGet(GLUT_OVER tchorYglutCreas thEnd(glutCrea}.
         }
       Iativi( thetInitWindBlutns w_LINE_LOOPglutCreathVesplx2ide chorXow tchorYglutCreathVesplx2ide chorXowsAMAGED)glutCreathVesplx2idsGLUT_OVERsAMAGED)glutCreathVesplx2idsGLUT_OVER tchorYglutCreathEnd(glutCrearGet(GLUT_OV =RsAMAGEDXlutCrearGet(GLUT_OY =RsAMAGEDY;e your program toNostceverla

       The overlay display callback can b

         menu
       stattWina has beallback p is saved fben whe GLUTeeeee;red. has ben b
       nred.
       ray(voibup misit in an uphutton forawOverlbenerateyou are idia, prevSayRedisplay

AUTH not set thisverlaydow, glutSetColor
GLUT                                                 3.7                     glutPostOverlayRedisplay(3GLUT)

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors
Report errors in the content of this documentation with the feedback links below.
Bug reports
Report bugs in the functionality of the described tool or API through Bug Reporter.
Formatting problems
Report formatting mistakes in the online version of these pages with the feedback links below.

Did this document help you? Yes It's good, but... Not helpful...