nanogui: Are we allowed to mandate GrFlush()?
Subject:
Re: [nanogui] Are we allowed to mandate GrFlush()?
From:
Jordan Crouse ####@####.####
Date:
7 Aug 2001 15:16:15 -0000
Message-Id: <01080709163700.11330@cosmic>
Most programs that don't care about buffering just draw to the screen, and
simply assume that the screen will be drawn in due time. And programs that
do care about buffering are usually writing to their own offscreen buffers
anyway, and do a blit when they are ready to refresh the screen.
In any case, a GrFlush would be probably unnessesary, as a simple program
wouldn't really care if there are a few microseconds between drawing
operations, and the buffered programs would have already taken it all into
consideration.
Jordan
On Tuesday 07 August 2001 09:06, Steven Stadnicki mentioned:
> I'm looking at what amounts to a double- or triple-buffered display
> system
> where the simplest scheme to handle what I want to do is to mandate the
> user to 'flush' from his primary output buffer to a display buffer. I'm
> thinking
> of trying to do this by making GrFlush not just a good idea but in fact
> mandatory after a set of draw operations when the user is ready to
> display
> to the screen, but I'm wondering if this is really legitimate, or
> whether too
> many programs assume that what they draw will automatically be displayed
>
> and don't bother calling GrFlush().
>
> Steven Stadnicki
> ####@####.####
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
