You are not logged in.

#1 2024-11-09 11:48:54

2handband
Member
Registered: 2011-01-21
Posts: 67

New Picom rules and transparency

I'm new to Picom, and it appears that every tutorial I can find, including the one on the Arch Wiki, is referring to what Picom calls the "old style rules". I tried to set up transparency/opacity utilizing those instructions, and Picom is throwing errors at me saying I should be using the new rules. I can't find any guides for that except the official Picom one, which I found to be confusing. Anyone know how to set up varying levels of transparency/opacity using the newer Picom rules?

Offline

#2 2024-11-09 16:08:27

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 73,800

Offline

#3 2024-11-09 22:53:00

2handband
Member
Registered: 2011-01-21
Posts: 67

Re: New Picom rules and transparency

My apologies. That said I've resolved most of the problem. I re-read the new window rules, and mostly figured it out, with one caveat I'm hoping someone can help me with. I added the following:


   {
  match = "focused"; 
  opacity = 0.9; 
}, {
  match = "!focused";
  opacity = 0.4;
},

The effect of which is to make my active window slightly transparent, with inactive windows highly transparent. HOWEVER, dmenu is taking on the transparency of the inactive window, which I don't care for at all. I tried to create the following rule:

{
  match = "name = 'dmenu'";
  opacity = 0.9;
},

It doesn't return any error messages, but it doesn't correct the problem, either. Any insight?

Offline

#4 2024-11-10 08:39:28

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 73,800

Re: New Picom rules and transparency

match = "class_i = 'dmenu'";

dmenu has a -name and a -class parameter that set the two values of WM_CLASS (class_i, class_g) and default to dmenu/Dmenu
Idk whether you can set WM_NAME as well.

Offline

Board footer

Powered by FluxBB