Lines Matching full:compositor
55 to the compositor. That event is followed by a number of descriptive
79 between windows), compositor-specific grab policies apply. This usually
104 compositor-specific policy when a tool can be removed. Common approaches
145 seat. After binding to this interface, the compositor sends a set of
181 object stays valid until the client destroys it; the compositor
362 It is compositor-dependent when a tool is removed. A compositor may
364 A compositor may also keep a tool alive until shutdown.
420 contact. On some devices, a compositor may not consider a tool in
431 and the compositor grab (if any) is dismissed.
434 with the surface of the tablet and the compositor does not have an
437 event and a wp_tablet.frame event. If the compositor has an ongoing
442 contact. On some devices, a compositor may not consider a tool out
519 clicks. The compositor may accumulate values smaller than a logical
541 button events are generated by the compositor. See
