Fix typo in XI2proto.txt

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
This commit is contained in:
Paul "TBBle" Hampson 2009-04-22 09:00:14 +10:00 committed by Peter Hutterer
parent 3380ae0ac0
commit 589dc6ffa5

View file

@ -79,7 +79,7 @@ If an event is generated by an SD
- if the SD is attached to a master keyboard, it sends events to this
keyboard's focus window (if applicable) and/or changes the modifier state of
this keyboard.
- if the SD is not attached to an SD ("floating"), it does not change
- if the SD is not attached to an MD ("floating"), it does not change
any master device. The SD has its own (invisible) sprite and its own focus.
Both the sprite and the focus must be managed explicitly by the client
program.
@ -639,7 +639,7 @@ XI2. Clients should ignore this data.
└───
This request actively grabs control of the specified input device. Further
input evens from this device are reported only to the grabbing client.
input events from this device are reported only to the grabbing client.
This request overides any previous active grab by this client for this
device.
@ -715,7 +715,7 @@ XI2. Clients should ignore this data.
Errors: Device, Value
The AllowDeviceEvents request releases some queued events if the client
The XIAllowEvents request releases some queued events if the client
has caused a device to freeze. The request has no effect if the specified
time is earlier than the last-grab time of the most recent active grab for
the client, or if the specified time is later than the current X server
@ -726,7 +726,7 @@ XI2. Clients should ignore this data.
AsyncDevice:
If the specified device is frozen by the client, event processing for that
device continues as usual. If the device is frozen multiple times by the
client on behalf of multiple separate grabs, AsyncThisDevice thaws for
client on behalf of multiple separate grabs, AsyncDevice thaws for
all.
AsyncDevice has no effect if the specified device is not frozen by the
client, but the device need not be grabbed by the client.