Skip to content
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

"focused" and "!focused" reversed #28

Closed
BigB00st opened this issue Jan 25, 2020 · 1 comment
Closed

"focused" and "!focused" reversed #28

BigB00st opened this issue Jan 25, 2020 · 1 comment
Labels
upstream Upstream issue not directly related to the dual-filter kawase blur

Comments

@BigB00st
Copy link

Platform: Arch 5.4.14 amd64

Drivers: mesa, xf86-video-intel

WM: i3-gaps

Compton version: vgit-e0149 (picom-tryone latest)

Compton configuration: https://pastebin.com/AaHv0vp5

Steps of reproduction

In opacity-rule, the programs are considered focused when they are not, and considered not focused when they are.

opacity-rule = [
  "55:class_g = 'Termite' && focused",
  "85:class_g = 'Termite' && !focused",
  "75:class_g = 'code-oss' && focused",
  "90:class_g = 'code-oss' && !focused"
];

Therefore, I gave higher opacity to non focused programs, and lower opacity to focused programs.

Expected behavior

Focused programs should be focused, and non focused programs shouldn't. When using compton before, I didn't face this problem.

Current Behavior & Other details

I use --experimental-backend, but the issue exists also without the flag.

@tryone144
Copy link
Owner

See this upsteam issue: yshui/picom#266

Some preliminary testing suggests that the change in yshui/picom@79fc36b with regard to the _NET_WM_CLIENT_OPACITY (see yshui/picom#134 for a discussion why) has introduced a race condition where the updated opacity value is actually one state behind (i.e. focused for unfocused windows and !focused for focused ones).

I suggest continuing the discussion in the upstream issue.

@tryone144 tryone144 added the upstream Upstream issue not directly related to the dual-filter kawase blur label Jan 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream Upstream issue not directly related to the dual-filter kawase blur
Projects
None yet
Development

No branches or pull requests

2 participants