Go to file
Yuxuan Shui a69ed89114
Treat first frame after redirection differently
Because first frame no window has their pixmap bound, which doesn't
happen in frames after the first. If a window is unmapped in that frame,
the compositor will try to render a window with no pixmap bound if
fading is enabled.

Now we keep track if we are in the first frame, and if that's the case
we skip fading in unmap/destroy.

Fixes #239, bug number 2

Signed-off-by: Yuxuan Shui <yshuiv7@gmail.com>
2019-09-29 00:40:09 +01:00
.circleci Run test cases in CI 2019-08-04 21:10:49 +01:00
.github issue template: use proper html comment 2019-08-18 01:34:18 +01:00
LICENSES More license stuff... 2018-10-04 11:18:09 +01:00
bin Fix small misspellings 2019-01-28 10:58:14 +01:00
dbus-examples Fix example dbus script after TYPE_ENUM change 2019-08-09 23:40:20 +01:00
man meson.build: rename build_docs to with_docs 2019-07-25 01:29:42 +01:00
media Added 48x48px raster of initial Compton logo 2015-09-17 21:57:11 -04:00
src Treat first frame after redirection differently 2019-09-29 00:40:09 +01:00
subprojects/test.h Vendor test.h 2019-08-04 13:49:28 +01:00
tests tests/issue239_2: add comments 2019-09-28 23:29:19 +01:00
.clang-format new glx: implement blur 2019-03-10 01:22:38 +00:00
.editorconfig Coding style change 2019-02-07 21:37:13 +00:00
.gitignore Update .gitignore 2019-08-09 23:40:41 +01:00
.gitmodules Vendor test.h 2019-08-04 13:49:28 +01:00
CONTRIBUTORS Update CONTRIBUTORS 2019-07-19 22:49:23 +01:00
COPYING More license stuff... 2018-10-04 11:18:09 +01:00
Doxyfile Fix small misspellings 2019-01-28 10:58:14 +01:00
LICENSE.spdx More license stuff... 2018-10-04 11:18:09 +01:00
README.md README: fix typo in debian deps 2019-09-19 16:02:44 +02:00
README_orig.md update readme 2018-04-16 10:13:55 -04:00
compton-default-fshader-win.glsl Feature: #183 custom window shader & #193 --no-fading-destroyed-argb 2014-05-16 15:18:17 +08:00
compton-fake-transparency-fshader-win.glsl Feature: #183 custom window shader & #193 --no-fading-destroyed-argb 2014-05-16 15:18:17 +08:00
compton.desktop added keywords to desktop entry 2019-08-18 20:59:47 -07:00
compton.sample.conf Deprecate --glx-swap-method 2019-03-12 00:35:47 +00:00
desc.txt Misc: #49: Add CMake support 2012-10-03 13:34:54 +08:00
functions.sh Misc: Move shared functions out of make-release.sh 2015-01-11 16:26:36 +08:00
make-release.sh Misc: Move shared functions out of make-release.sh 2015-01-11 16:26:36 +08:00
meson.build meson.build: make git version string less confusing 2019-07-30 22:22:21 +01:00
meson_options.txt meson.build: rename build_docs to with_docs 2019-07-25 01:29:42 +01:00

README.md

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

Call for testers

--experimental-backends

This flag enables the refactored/partially rewritten backends.

Currently new backends features better vsync with the xrender backend, improved input lag with the glx backend (for non-NVIDIA users). The performance should be on par with the old backends.

New backend features will only be implemented on the new backends from now on, and the old backends will eventually be phased out after the new backends stabilizes.

To test the new backends, add the --experimental-backends flag to the command line you used to run compton. This flag is not available from the configuration file.

To report issues with the new backends, please state explicitly you are using the new backends in your report.

Change Log

See Releases

Build

Dependencies

Assuming you already have all the usual building tools installed (e.g. gcc, python, 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
  • pixman
  • libdbus (optional, disable with the -Ddbus=false meson configure flag)
  • libconfig (optional, disable with the -Dconfig_file=false meson configure flag)
  • libxdg-basedir (optional, disable with the -Dconfig_file=false meson configure flag)
  • libGL (optional, disable with the -Dopengl=false meson configure flag)
  • libpcre (optional, disable with the -Dregex=false meson configure flag)
  • libev
  • uthash

On Debian based distributions (e.g. Ubuntu), the list of needed packages are

libxext-dev libxcb1-dev libxcb-damage0-dev libxcb-xfixes0-dev libxcb-shape0-dev libxcb-render-util0-dev libxcb-render0-dev libxcb-randr0-dev libxcb-composite0-dev libxcb-image0-dev libxcb-present-dev libxcb-xinerama0-dev libpixman-1-dev libdbus-1-dev libconfig-dev libxdg-basedir-dev libgl1-mesa-dev  libpcre2-dev  libevdev-dev uthash-dev libev-dev

To build the documents, you need asciidoc

To build

$ git submodule update --init --recursive
$ meson --buildtype=release . build
$ ninja -C build

Built binary can be found in build/src

If you have libraries and/or headers installed at non-default location (e.g. under /usr/local/), you might need to tell meson about them, since meson doesn't look for dependencies there by default.

You can do that by setting the CPPFLAGS and LDFLAGS environment variables when running meson. Like this:

$ LDFLAGS="-L/path/to/libraries" CPPFLAGS="-I/path/to/headers" meson --buildtype=release . build

As an example, on FreeBSD, you might have to run meson with:

$ LDFLAGS="-L/usr/local/include" CPPFLAGS="-I/usr/local/include" meson --buildtype=release . build
$ ninja -C build

To install

$ ninja -C build install

Default install prefix is /usr/local, you can change it with meson configure -Dprefix=<path> build

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.

Contributions to the documents and wiki will also be appreciated.

Contributors

See CONTRIBUTORS