Lines Matching refs:clobber

133     Returned in the <event_type> field of a "buffer clobber" event:
138     Returned in the <draw_type> field of a "buffer clobber" event:
143     Returned in the <mask> field of a "buffer clobber" event:
347     either case, the client can register to receive a "buffer clobber" event
377     with only asynchronous notification (via the "buffer clobber" event), the 
384     queue for "buffer clobber" events (assuming that these events had been 
446     A single X server operation can cause several "buffer clobber" events to be
448     clobber" events to be generated). Each event specifies one region of the
450     which color or ancillary buffers were affected. All the "buffer clobber"
455     For "preserved" pbuffers, a "buffer clobber" event, with <type>
458     pbuffer were affected. Clients who receive many "buffer clobber" events,
463     For an "unpreserved" pbuffer a "buffer clobber" event, with <type>
467     For Windows, "buffer clobber" events, with <type> GLX_DAMAGED_SGIX or
475     each client that requested "clobber events" for <drawable>.