[PATCH compositeproto] Remove {Redirect, Transform}Coordinate requests

Daniel Martin consume.noise at gmail.com
Mon Jan 21 22:34:41 PST 2013

Remove the RedirectCoordinate and TransformCoordinate requests from the
specification. The corresponding events and structures had been removed
in July 2007:
    commit 1838412 Define new manual-redirect clipping semantics and
                   bump version to 0.4.

Reference-to: 1838412121d0bac8ce443d362e75439d58a93a4d

Signed-off-by: Daniel Martin <consume.noise at gmail.com>
Just found this while skimming through the protocol specs for xcb/proto
to get a clue what's missing.

 compositeproto.txt | 40 ----------------------------------------
 1 file changed, 40 deletions(-)

diff --git a/compositeproto.txt b/compositeproto.txt
index 4b86621..c1d099c 100644
--- a/compositeproto.txt
+++ b/compositeproto.txt
@@ -297,43 +297,3 @@ operations other than QueryVersion.
     Composite Overlay Window on the screen specified by the 
     argument 'window'. A screen's Composite Overlay Window is 
     unmapped when there are no longer any clients using it.
-12. External coordinate transformation (0.4 and later)
-    RedirectCoordinate
-		window:				Window
-		redirect:			BOOL
-		errors: Window, Access
-	If 'redirect' is TRUE, the requesting client is placed in charge of
-	coordinate transformations between 'window' and its children. If
-	'redirect' is FALSE, any such redirection is disabled. Any
-	transformations needed by the server will be delivered to the
-	requesting client in TransformCoordinateNotify events and the
-	requesting client must reply with matching TransformCoordinate
-	requests for the server to continue with the operation.
-	Generates an 'Access' error if another client has
-	redirected coordinates for 'window'.
-    TransformCoordinate
-		window:				Window
-		serialNumber:			CARD32
-		x, y:				INT16
-		coordinates:			LISTofCompositeCoordinate
-	This provides the transformation data needed by the server for a
-	single TransformCoordinateNotify event. 'serialNumber' must match
-	the serial number delivered in the event. 'x' and 'y' represent the
-	coordinate from the event relative to the 'window'. 'coordinates'
-	represent the coordinate from the event relative to each child
-	listed. Any children not listed in 'coordinates' are given the
-	default transformation using the child window position within the
-	parent as a simple translation.
-	The result of this is that any pointer data seen by means of
-	the protocol will appear to reflect the transformation
-	performed by this request.

More information about the xorg-devel mailing list