diff options
| author | Peter Hutterer <peter.hutterer@who-t.net> | 2010-01-11 17:02:55 +1000 |
|---|---|---|
| committer | Peter Hutterer <peter.hutterer@who-t.net> | 2010-08-06 10:11:43 +1000 |
| commit | 993ca70d7ecfb88037edfd77bccfcb671aea4c7b (patch) | |
| tree | c8ddee544109da773c5cbc9b0ea0f4b3d3aedb5e | |
| parent | 617c4a2db48e98d06f728fa6b8caa18fbbfb66fc (diff) | |
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 <peter.hutterer@who-t.net>
Reviewed-by: Fernando Carrijo <fcarrijo@yahoo.com.br>
| -rw-r--r-- | XIproto.txt | 4 |
1 files changed, 3 insertions, 1 deletions
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 |