62d4c0cbdb
Previously if we unredirect the screen while a fading is in progress, we will "resume" the fading when we redirect the screen again. This is usually fine unless the window being faded out is destroyed. we still tries to fade it out, but since we don't have the pixmap of the window anymore (freed by unredirect), we will generate lots of errors until the window is completely "faded out". Also this change makes it easy to reason about things. Now we know when the screen is unredirected, all the windows can either be in MAPPED or UNMAPPED state, nothing else. Signed-off-by: Yuxuan Shui <yshuiv7@gmail.com>
Compton
This is a development branch, bug to be expected
This is forked from the original Compton because that seems to have become unmaintained.
The current battle plan of this fork is to refactor it to make the code possible to maintain, so potential contributors won't be scared away when they take a look at the code.
We also try to fix bugs.
The original README can be found here
Changelog
See Releases
Build
Dependencies
Assuming you already have all the usual building tools installed (e.g. gcc, meson, ninja, etc.), you still need:
- libx11
- libx11-xcb
- libXext
- xproto
- xcb
- xcb-damage
- xcb-xfixes
- xcb-shape
- xcb-renderutil
- xcb-render
- xcb-randr
- xcb-composite
- xcb-image
- xcb-present
- xcb-xinerama (optional, disable with the
-Dxinerama=falsemeson configure flag) - pixman
- libdbus (optional, disable with the
-Ddbus=falsemeson configure flag) - libconfig (optional, disable with the
-Dconfig_file=falsemeson configure flag) - libxdg-basedir (optional, disable with the
-Dconfig_file=falsemeson configure flag) - libGL (optional, disable with the
-Dopengl=falsemeson configure flag) - libpcre (optional, disable with the
-Dregex=falsemeson configure flag) - libev
To build the documents, you need asciidoc
How to build
$ meson --buildtype=release . build
$ ninja -C build
Built binary can be found in build/src
How to Contribute
Code
You can look at the Projects page, and see if there is anything interests you. Or you can take a look at the Issues.
Non-code
Even if you don't want to contribute code, you can still contribute by compiling and running this branch, and report any issue you can find.
Contributors
See CONTRIBUTORS