[Xcb] xcb_wait/poll_for_event(): why not flush?

[Ian Osgood]

Good point. I'll add xcb_aux_wait/poll_for_event() with appropriate  
warning comments.

Ian

On Nov 10, 2006, at 9:16 AM, Barton C Massey wrote:

> Philosophically, I'm not too up for gratuitously flushing
> the buffer; in a program with a separate event thread, it
> would likely be unwanted, and would represent a potential
> race in any case.
>
> Having a convenience function that called xcb_flush() then
> xcb_*_for_event() that single-threaded programs could use
> would probably be the right way here.
>
> 	Bart
>
> In message <13812E9C-4C77-4B36-BE0C-DA1AD541A309 at quirkster.com> you  
> wrote:
>> Apparently, one of XNextEvent()'s effects is to flush the output
>> buffer. Is there a reason that xcb_wait/poll_for_event() doesn't do
>> the same thing? Looking at the XCB demo code, this would eliminate
>> many boilerplate uses of xcb_flush().  By the way, xcb_wait_for_reply
>> () does flush like this.
>>
>> Ian
>>
>> _______________________________________________
>> Xcb mailing list
>> Xcb at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/xcb
> _______________________________________________
> Xcb mailing list
> Xcb at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/xcb
>