The tests also use some non-existing events to check that these are
handled correctly. Then came XI 2.4 and introduced several new events,
which broke the test.
Fix this by updating the test accordingly.
This means tests will now fail when using an older version of xcb-proto.
If you are affected by this, either do not run tests, or build against a
newer version of xcb-proto.
Signed-off-by: Uli Schlachter <psychon@znc.in>
The highest bit of an event code shows if the event was generated by the X11
server or via the SendEvent request. Ignore this bit in all places that handle
event codes.
Signed-off-by: Uli Schlachter <psychon@znc.in>
Now that there are three different functions for querying information about
events, there shouldn't be one which monopolizes on the "_for_event" name.
Instead, the preferred API is the "_for_xcb_event" function.
Signed-off-by: Uli Schlachter <psychon@znc.in>
This function compares strings, handles NULL (almost) correctly, prints an error
if a mismatch occurs and returns a suitable int result.
Signed-off-by: Uli Schlachter <psychon@znc.in>
This is based on util-cursor's build system and libxcb/configure.ac for finding
xcb-proto's XML files.
Signed-off-by: Uli Schlachter <uli.schlachter@informatik.uni-oldenburg.de>
