Re: [compiz] Re: BSO paint values - was window matching interface and the new match option

2007-02-28 Thread David Reveman
On Tue, 2007-02-27 at 17:31 +0100, Danny Baumann wrote: Hi, obs does not appear to listen for the client messages, so I assume that there is a separate code path in core which does a very similar thing to your changeWindowOpacity function? Indeed. This is done in core's event.c.

[compiz] Re: BSO paint values - was window matching interface and the new match option

2007-02-27 Thread Mike Dransfield
Danny Baumann wrote: It's slightly different. Whenever a client wants to change an atom (such as opacity), it sends a client message with the request to the WM which then decides to modify the actual X property or to ignore it. Whenever there is a client message requesting an

[compiz] Re: BSO paint values - was window matching interface and the new match option

2007-02-27 Thread Danny Baumann
Hi, obs does not appear to listen for the client messages, so I assume that there is a separate code path in core which does a very similar thing to your changeWindowOpacity function? Indeed. This is done in core's event.c. Are you planning to pull all of that out into a plugin too? Hmm,