For some reason, the X "expose" event handler was *directly* calling

the display handler in the client.  (Okay, it was calling a function
that operates on the window handle.)

If you have any complexity to the display code, this can be painful
to watch.  I can't think of a good reason to do the display immediately,
so I fixed the code to do a glutPostRedisplay().


git-svn-id: https://svn.code.sf.net/p/freeglut/code/trunk@461 7f0cb862-5218-0410-a997-914c9d46530a
This commit is contained in:
rkrolib 2004-02-14 03:29:57 +00:00
parent 70f0afbc07
commit c03f197329

View File

@ -613,12 +613,13 @@ void FGAPIENTRY glutMainLoopEvent( void )
* XXX double-buffered does not respect viewport when we * XXX double-buffered does not respect viewport when we
* XXX do a buffer-swap). * XXX do a buffer-swap).
* *
* XXX GETWINDOW( xexpose );
* XXX fgSetWindow( window );
* XXX glutPostRedisplay( );
*/ */
if( event.xexpose.count == 0 ) if( event.xexpose.count == 0 )
fghRedrawWindowByHandle( event.xexpose.window ); {
GETWINDOW( xexpose );
fgSetWindow( window );
glutPostRedisplay( );
}
break; break;
case MapNotify: case MapNotify: