Bernd Busse

IIRC, the pattern matching only supports a limited set of atom-types for the properties, namely integers and string variants as well as X atoms (i.e. integer atom ids). By the...

Sorry for the late reply. I am not entirely sure why `xcb_get_property_reply` returns `NULL`. I tested this locally using our own utility function `x_get_prop()` and that works fine. You are...

> do you have any example of how did you implement that? See https://github.com/tryone144/picom/commit/c349a92a5b2ff63d4dc31fbd0e9f3c2bced96068. This is just the functionality, no changes to the documentation yet.

I think instead of providing another (OpenGL-specific) configuration option, this is better solved by overriding the behaviour in the window shader. This is currently not yet implemented for the experimental...

Interesting behaviour. I'm not shure, what exactly could cause this. It seems however, you are using my original port to the old compton codebase. Maybe you could try if my...

Hi, What branch are you using? I guess you installed the [AUR package](https://aur.archlinux.org/packages/compton-tryone-git/) based on the older [dual_kawase](https://github.com/tryone144/compton/tree/dual_kawase) branch. You may try the newer [improved_fbo](https://github.com/tryone144/compton/tree/improved_fbo) branch and see if the...

Yeah, as far as I can tell from a quick look, yshui's fork has a “new” callback to handle root window resizes. As my newer branch is still based on...

> According to the README.md here at this fork, `dual_kawase` blur "only works with `--experimental-backends` and `--backend glx`". However, with glx set either at runtime through `--backend` or in the...

Can you re-check with a clean build from https://github.com/tryone144/picom/tree/feature/dual_kawase? This is the PR-branch rebased against the current picom head. Sadly I can't reproduce this with with my nvidia-based setup.

@frebib is the maintainer of the PKGBUILD in the AUR. Looks, like a problem with the automatic rebase onto the `yshui/next` branch. Possible brute-force workaround would be to run a...