-
-
Notifications
You must be signed in to change notification settings - Fork 584
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shaders don't apply to all windows on BSPWM #1174
Comments
could you do |
Here's the output from diff
|
do windows that shader does/doesn't apply to running bspwm have something common? for some reason, i'm thinking about their depths (you can check a window's depth using |
Yeah polybar and zim have different depths. Polybar has depth of 32 and zim had 24. I took info in both bspwm and i3 in case it's useful. polybar in bspwm
zim in bspwm
polybar in i3
zim in i3
|
However I noticed that the kitty terminal also has a depth of 32, but doesn't seem to be affected when I run with --window-shader-fg ~/.config/picom/testShader.glsl in bspwm. xwininfo for kitty in bspwm
|
does it happen with |
does #1179 fix the issue for you? |
Hello, sorry for the late reply I've been away for a couple of days. I've built and tested #1179 and I'm pleased to say it works! I also tested using --config=/dev/null (with the version from my package manager) and that also applied the shader correctly. Thank you for all your help! |
…e function Image decouple should keep all the image properies from the source image, so shader must be copied. And there are also some internal properties what should be inherited but wasn't. In particular this prevents images from losing their shaders when alpha is applied. Fixes yshui#1174
…e function Image decouple should keep all the image properies from the source image, so shader must be copied. And there are also some internal properties what should be inherited but wasn't. In particular this prevents images from losing their shaders when alpha is applied. Fixes #1174 (cherry picked from commit eb39426) Signed-off-by: Yuxuan Shui <yshuiv7@gmail.com>
…e function Image decouple should keep all the image properies from the source image, so shader must be copied. And there are also some internal properties what should be inherited but wasn't. In particular this prevents images from losing their shaders when alpha is applied. Fixes #1174 (cherry picked from commit eb39426) Signed-off-by: Yuxuan Shui <yshuiv7@gmail.com>
Platform
Arch Linux x86_64
GPU, drivers, and screen setup
Intel UHD Graphics on a single monitor (built into laptop)
xf86-video-vesa: 2.6.0-1
mesa: 1:23.3.4-2
Environment
I am using BSPWM as my window manager.
picom version
Configuration:
Configuration file
picom.conf
testShader.glsl
Steps of reproduction
Expected behavior
All open windows should turn solid pink.
Current Behavior
Only polybar and drop down menus appear to turn pink.
Other details
This issue appears to be exclusive to BSPWM. I've tried to reproduce the issue in i3 and the shader works as expected.
running picom --backend glx --window-shader-fg ~/.config/picom/testShader.glsl in i3 results in:
running picom --backend glx in i3 with a rule in my config file to only target Zim results in:
The text was updated successfully, but these errors were encountered: