chjj / compton

A compositor for X11.
Other
2.25k stars 498 forks source link

Is there a way to disable fading when switching workspace? #314

Open Toqozz opened 9 years ago

Toqozz commented 9 years ago

I've looked extensively for an option (or a way to exclude workspaces/desktops).

Would really love this, as it makes fading quite jarring -- but I can live without the feature.

If it is relevant, my WM is bspwm.

danijar commented 8 years ago

+1

raehik commented 8 years ago

This has only just started happening for me (i3). I use compton --vsync opengl. Noticed it this morning. Any info would be great!

richardgv commented 8 years ago

I will look into this after I take care of the bugs, but I am afraid it would not be too soon.

Meanwhile, you could try --no-fading-openclose, which does disable fading during workspace switches for i3-4.12 -- but it disables fading when opening/closing windows, too. Eeeh, probably not the most desirable behavior.

xaviervalarino commented 7 years ago

@Toqozz I am also using Bspwm, and had success removing fading when switching between workspaces by adding --no-fading-openclose = true as suggested by @richardgv.

krompus commented 6 years ago

I still have this issue (Arch+i3wm), and I've been looking for a way to fix it. The only thing I need compton for is the true transparency; no desire for any kind of fading, and the issue persists despite my attempted fixes. I've got the no-fading-openclose = true thing in my config, as well as other options for disabling fading. Here's my config.

Here's a screenrec showing the persistent issue.

Perhaps someone could take a look at my config, and let me know if there's something missing or incorrect? Thanks!

ndegruchy commented 5 years ago

I am having this issue, too. I've defined the --no-fading-openclose on compton on launch, but it still seems to happen. When I kill and respawn compton with those options, it seems to work when switching between existing windows, but switching to an empty workspace in i3 triggers the fading coming back (for all windows/workspaces).

I launch compton with compton --use-ewmh-active-win --no-fading-openclose --no-dock-shadow --no-dnd-shadow --unredir-if-possible --backend glx --daemon &. I currently don't use a config file as this launches from my .xsession file.

Which is as follows:

export GTK2_RC_FILES=$XDG_CONFIG_HOME/gtk-2.0/gtkrc
systemctl --user import-environment DISPLAY &
numlockx &
redshift &
hsetroot -fill "$HOME/Pictures/Wallpaper/forested-mountains.jpg" &
setxkbmap -option 'ctrl:nocaps' &
xautolock -locker "$HOME/.local/bin/lock" &
udiskie --no-automount --notify --tray --menu flat --no-file-manager &
compton --use-ewmh-active-win --no-fading-openclose=true --no-dock-shadow --no-dnd-shadow --unredir-if-possible --backend glx --daemon &
dunst &

exec i3
vevais commented 5 years ago

I am having the same issue with awesomewm. Is there any fix to this by now?

yochaigal commented 5 years ago

I would also like to know of any workarounds to this. Compton is beautiful in XFCE 4.12; if only I could change workspaces without seeing my desktop!

ngortheone commented 4 years ago

@yochaigal @vevais @ndegruchy @Toqozz @danijar Try --fade-in-step=1 --fade-out-step=1 --fade-delta=0, seems to be working for me

yochaigal commented 4 years ago

@ngortheone this did not work for me. Particularly using Remmina in fullscreen mode (not sure if that's relevant); when I switch workspaces it flashes the bright purple wallpaper I use.

yochaigal commented 4 years ago

Here is a video, in case others were interested in what it looks like:

https://imgur.com/5i7Nkwp

pfrenssen commented 4 years ago

I can confirm that the background also flashes for me exactly like shown in the screencast posted by @yochaigal .

On a side note, shouldn't we open a sister issue at https://github.com/yshui/picom and move this discussion there? The active development is happening there. This repo hasn't seen any changes since 2017.

yochaigal commented 4 years ago

On a side note, shouldn't we open a sister issue at https://github.com/yshui/picom and move this discussion there? The active development is happening there. This repo hasn't seen any changes since 2017.

I had no idea this was the case. Yes, we absolutely should move it there.