mirror of
https://github.com/X11Libre/xserver.git
synced 2026-03-24 01:34:11 +00:00
Xi: inline SProcXIPassiveGrabDevice() and SProcXIPassiveUngrabDevice()
Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
This commit is contained in:
committed by
Enrico Weigelt
parent
7a0efe7da5
commit
7d9fb7b4a0
@@ -145,7 +145,7 @@ request_XIGetSelectedEvents(xXIGetSelectedEventsReq * req, int error)
|
||||
The handler proc's don't use that field anymore, thus also SProc's
|
||||
wont swap it. But this test program uses that field to initialize
|
||||
client->req_len (see above). We previously had to swap it here, so
|
||||
that SProcXIPassiveGrabDevice() will swap it back. Since that's gone
|
||||
that ProcXIPassiveGrabDevice() will swap it back. Since that's gone
|
||||
now, still swapping itself would break if this function is called
|
||||
again and writing back a errornously swapped value
|
||||
*/
|
||||
|
||||
@@ -151,7 +151,7 @@ request_XIPassiveGrabDevice(ClientPtr client, xXIPassiveGrabDeviceReq * req,
|
||||
The handler proc's don't use that field anymore, thus also SProc's
|
||||
wont swap it. But this test program uses that field to initialize
|
||||
client->req_len (see above). We previously had to swap it here, so
|
||||
that SProcXIPassiveGrabDevice() will swap it back. Since that's gone
|
||||
that ProcXIPassiveGrabDevice() will swap it back. Since that's gone
|
||||
now, still swapping itself would break if this function is called
|
||||
again and writing back a errornously swapped value
|
||||
*/
|
||||
@@ -172,7 +172,7 @@ request_XIPassiveGrabDevice(ClientPtr client, xXIPassiveGrabDeviceReq * req,
|
||||
swapl(mod);
|
||||
}
|
||||
|
||||
rc = SProcXIPassiveGrabDevice(&client_request);
|
||||
rc = ProcXIPassiveGrabDevice(&client_request);
|
||||
assert(rc == error);
|
||||
|
||||
if (rc != Success)
|
||||
|
||||
@@ -114,7 +114,7 @@ request_XISelectEvent(xXISelectEventsReq * req, int error)
|
||||
The handler proc's don't use that field anymore, thus also SProc's
|
||||
wont swap it. But this test program uses that field to initialize
|
||||
client->req_len (see above). We previously had to swap it here, so
|
||||
that SProcXIPassiveGrabDevice() will swap it back. Since that's gone
|
||||
that ProcXIPassiveGrabDevice() will swap it back. Since that's gone
|
||||
now, still swapping itself would break if this function is called
|
||||
again and writing back a errornously swapped value
|
||||
*/
|
||||
|
||||
@@ -74,7 +74,7 @@ request_XISetClientPointer(xXISetClientPointerReq * req, int error)
|
||||
The handler proc's don't use that field anymore, thus also SProc's
|
||||
wont swap it. But this test program uses that field to initialize
|
||||
client->req_len (see above). We previously had to swap it here, so
|
||||
that SProcXIPassiveGrabDevice() will swap it back. Since that's gone
|
||||
that ProcXIPassiveGrabDevice() will swap it back. Since that's gone
|
||||
now, still swapping itself would break if this function is called
|
||||
again and writing back a errornously swapped value
|
||||
*/
|
||||
|
||||
Reference in New Issue
Block a user