nanogui: Make nano-X calls synchronous?
Subject:
Re: [nanogui] Make nano-X calls synchronous?
From:
"Greg Haerr" ####@####.####
Date:
22 Aug 2007 17:53:24 +0100
Message-Id: <0e1401c7e4dc$df206a10$6401a8c0@winXP>
: No, actually I was trying to measure the FPS when doing some bitblt
: operations, and it just queued everything in the server and the screen
: was still flickering even after the client was killed.
Sorry, I get it now, synchronous drawing operations per client
request. In the original client/server design, all 'void' type
GrXXX operations (of which almost all drawing operations are void),
are locally queued by the client library, and then sent in one batch
to the server, with no way of waiting for completion. Any non-void
operation will wait, without the possibility of another request executing
until the return values are written back.
You might use GrFlush() inbetween each draw operation; this will
force the command to be written to the pipe. After that, its up
to the OS scheduler as to which process runs.
Regards,
Greg
