From 993ca70d7ecfb88037edfd77bccfcb671aea4c7b Mon Sep 17 00:00:00 2001 From: Peter Hutterer Date: Mon, 11 Jan 2010 17:02:55 +1000 Subject: Define the error cases for XSetDeviceMode better. Take the error codes as described in the man page for XSetDeviceMode. This is more likely to be what clients expect, especially since the protocol spec doesn't actually define when BadMode is to be reported. This behaviour is the same as specified in the XSetDeviceMode man page. Signed-off-by: Peter Hutterer Reviewed-by: Fernando Carrijo --- XIproto.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/XIproto.txt b/XIproto.txt index 20cc02a..f9d19f0 100644 --- a/XIproto.txt +++ b/XIproto.txt @@ -577,7 +577,9 @@ already has the device open with a different mode. It will fail and return AlreadyGrabbed if another client has the device grabbed. The request will fail with a BadMatch error if the - requested mode is not supported by the device. + device has no valuators and reports no axes of motion. The + request will fail with a BadMode error if the requested mode + is not supported by the device. SetDeviceMode device:DEVICE -- cgit v1.2.3