Bug 378 - man pages for XSelectInput and XMapWindow should document ordering issue
Summary: man pages for XSelectInput and XMapWindow should document ordering issue
Alias: None
Product: xorg
Classification: Unclassified
Component: Documentation (show other bugs)
Version: unspecified
Hardware: All All
: low trivial
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
Whiteboard: 2011BRB_Reviewed
Keywords: love
Depends on:
Reported: 2004-03-26 22:40 UTC by Alan Coopersmith
Modified: 2018-08-10 21:37 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description Alan Coopersmith 2004-03-26 22:40:43 UTC
The man pages for XSelectInput and XMapWindow should indicate that XSelectInput
should be called before XMapWindow, to avoid losing Expose events. See O'Reilly,
for example, in volume 2 man page for XMapWindow:

	"The client should call XSelectInput() for exposure events, then map,
	 then process input events.  The client's normal response to an Expose
	 event should be to repaint the window.  If you fail to wait for the
	 Expose event before drawing, the drawing may not appear in the window."

[Originally reported to Sun as Sun bug id #4333109.]
Comment 1 Erik Andren 2006-03-10 08:55:17 UTC
Is this implemented in a current version of xorg?
Comment 2 Alan Coopersmith 2006-03-11 11:46:39 UTC
Nope - still waiting for someone to write the text to put in the man pages.
Comment 3 Daniel Stone 2007-02-27 01:23:21 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 4 GitLab Migration User 2018-08-10 21:37:27 UTC
-- 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/lib/libx11/issues/75.

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.