3a054fccd1
xnestWindowExposures() is a micro-optimization for the specific case that a newly created window receives exposure events (from our upstream server) inside the region we're already exposing on our own (miWindowExposures()): it peeks the Xlib event queue for all expose events, checks whether their areas are inside our exposure region and requeue's those that aren't. Unfortunately, this depends on Xlib's internal queue mechamism, thus standing in the way of moving to XCB (which doesn't have that). Removing this doens't seem to make any practical difference, even with demanding applications like GIMP. The only cost is potentially having some initial window content painted twice, *if* the application really draws something complicated right after creating the window. *If* there'll really be a demand for such an optimization some day, it can be reimplemented without any message queue: just redirecting all expose events into recording them in a region, which is flushed out later. But for now, there really doesn't seem to be any practical need for that. Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net> |
||
|---|---|---|
| .gitlab-ci | ||
| Xext | ||
| Xi | ||
| composite | ||
| config | ||
| damageext | ||
| dbe | ||
| dix | ||
| doc | ||
| dri3 | ||
| exa | ||
| fb | ||
| glamor | ||
| glx | ||
| hw | ||
| include | ||
| man | ||
| mi | ||
| miext | ||
| os | ||
| present | ||
| pseudoramiX | ||
| randr | ||
| record | ||
| render | ||
| test | ||
| xfixes | ||
| xkb | ||
| .appveyor.yml | ||
| .dir-locals.el | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .travis.yml | ||
| COPYING | ||
| README.md | ||
| meson.build | ||
| meson_options.txt | ||
| xorg-server.m4 | ||
| xorg-server.pc.in | ||
| xserver.ent.in | ||
X Server
The X server accepts requests from client applications to create windows, which are (normally rectangular) "virtual screens" that the client program can draw into.
Windows are then composed on the actual screen by the X server (or by a separate composite manager) as directed by the window manager, which usually communicates with the user via graphical controls such as buttons and draggable titlebars and borders.
For a comprehensive overview of X Server and X Window System, consult the following article: https://en.wikipedia.org/wiki/X_server
All questions regarding this software should be directed at the Xorg mailing list:
https://lists.freedesktop.org/mailman/listinfo/xorg
The primary development code repository can be found at:
https://gitlab.freedesktop.org/xorg/xserver
For patch submission instructions, see:
https://www.x.org/wiki/Development/Documentation/SubmittingPatches
As with other projects hosted on freedesktop.org, X.Org follows its Code of Conduct, based on the Contributor Covenant. Please conduct yourself in a respectful and civilized manner when using the above mailing lists, bug trackers, etc: