diff options
| author | Daniel Stone <daniel@fooishbar.org> | 2008-10-28 16:27:37 +1100 |
|---|---|---|
| committer | Daniel Stone <daniel@fooishbar.org> | 2009-01-22 15:08:58 +1100 |
| commit | 1d1a0f67eee330a286fbdef17e967ce8ea201548 (patch) | |
| tree | adc801c8a67e53831f2272385e9c6ea812e374b7 /include | |
| parent | b5242789edb726bb539e4d42fa35bfdaca0025c9 (diff) | |
Xi: Introduce XIShouldNotify
XIShouldNotify just lets you know if you should send an event for a
keymap change (or similar) concerning a given device to a given client;
at the moment, this is only for devices which are sending events to that
client.
Signed-off-by: Daniel Stone <daniel@fooishbar.org>
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Diffstat (limited to 'include')
| -rw-r--r-- | include/exevents.h | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/include/exevents.h b/include/exevents.h index 8ddfbf9e8..abe1a5f23 100644 --- a/include/exevents.h +++ b/include/exevents.h @@ -255,4 +255,9 @@ extern _X_EXPORT int XIPropToFloat( float **buf_return ); +/* For an event such as MappingNotify which affects client interpretation + * of input events sent by device dev, should we notify the client, or + * would it merely be irrelevant and confusing? */ +extern _X_EXPORT int XIShouldNotify(ClientPtr client, DeviceIntPtr dev); + #endif /* EXEVENTS_H */ |