The PointerRoot (= 1) constant is missing from xproto.xml, so it's not in the headers either. However it's mentioned in the docs. It's only used for xcb_set_input_focus().
Sorry, what? $ grep -r XCB_INPUT_FOCUS_POINTER_ROOT /usr/include/xcb/xproto.h XCB_INPUT_FOCUS_POINTER_ROOT = 1, From xproto.xml: <!-- used for revert_to and focus --> <enum name="InputFocus"> <item name="None"> <value>0</value></item> <item name="PointerRoot"><value>1</value></item> <item name="Parent"> <value>2</value></item> <!-- revert_to only --> <item name="FollowKeyboard"><value>3</value></item> <!-- xinput extension only --> <doc> [...] </doc> </enum>
Those are the options for "revert_to", not "focus" For focus from the docs: The window to focus. All keyboard events will be reported to window. The window must be viewable (TODO), or a match_error_t occurs (TODO). focus is XCB_NONE (TODO), all keyboard events are discard‐until a new focus window is set. focus is XCB_POINTER_ROOT (TODO), focus is on the root of the screen on which the pointer is on currently.
(In reply to sigstop from comment #2) > Those are the options for "revert_to", not "focus" > > For focus from the docs: > > The window to focus. All keyboard events will be reported to window. The > window must be viewable (TODO), or a match_error_t occurs (TODO). > > focus is XCB_NONE (TODO), all keyboard events are discard‐until a new focus > window is set. > > focus is XCB_POINTER_ROOT (TODO), focus is on the root of the screen on > which the pointer is on currently. Um, sorry, I missed " <!-- used for revert_to and focus -->", however then the documentation is wrong still.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/proto/xcbproto/issues/6.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.