Yuxuan Shui
Yuxuan Shui
@DarioDarko can you provide your config file?
@enderprism hmm, i can't reproduce it. do you mind open an issue? please include a `--log-level=trace` log if you do. @DarioDarko can you do the same as well? thanks.
Well use ARGB "as needed" means if say the titlebar is transparent, awesome should use ARGB. Some compositors (such as compton) uses the lack of ARGB-ness of the frame window...
You've made some good points. I guess I will give up. > RGB clients can have a shape mask with holes. Compton fails miserably to handle those properly except for...
> people can do "crazy stuff" in their config. yeah... but current situation is suboptimal for people who don't do "crazy stuff", which would be most of us. I think...
In fact it should be more flexible, lua code should be able to specify if it needs a argb visual when a titlebar or a drawin is created.
@Elv13 yes, this will. alternatively we can also keep the default and add an option to enable this behavior, maybe `--argb-if-needed`.
So in summary, I think there is indeed a memory leak in picom, probably hidden in an error path which is only triggered by LeftWM. What I am interested to...
hmmm, thanks for the patch, but i want to understand this problem better. what corner radius did you use to get these screenshots?
hmm, i wonder if the off by 1 error is actually here: ```c if (rect_distance > 0.0f) { // -0.5f) { //