You are not logged in.

#1 2013-05-30 15:26:03

stackptr
Member
Registered: 2013-05-29
Posts: 4
Website

Communication between awesome and compton

Since awesome-related IRC/mailinglists are rather inactive, I wanted to post this question here first, since I know a lot of Archers use awesome.

Right now I'm using awesome 3.5.1 in [community] and compton-git from AUR. I'm invoking compton to provide transitions and drop-shadows to windows, which works pretty well except on one caveat: when tiling, drop shadows are rather troublesome. I wish to disable them, but only when tiling.

Hence, I need to figure out a way for awesome to talk to compton in order to achieve this.

From awesome's side, it seems I can achieve some communication via rules or signals. I'm more familiar with rules than signals, so I decided to start there. I can create a rule to change a window property when floating = false, which I assume to be the case for tiled windows. The problem is figuring out which window property to change on this condition.

From compton's side, there is an argument --shadow-exclude which takes a condition that allows me to specify a window property to match. It accepts other conditions, most of which are foreign to me.

Thus, I want to find a window property that can be changed through awesome and read through compton, and will not otherwise affect the window (for example, both programs can handle WINDOW_TYPE but I'm warned that changing that will lead to weird situations). I've been reading X documentation and playing around with xprop for the past hour with no luck. I'm looking for any bright ideas on what to do, as I'm convinced this can be done.

Thanks.


Freenode: mu

Offline

Board footer

Powered by FluxBB