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>