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 opacity/saturation/brightness change, compiz changes the paint modifier (w->paint) and sets the atom. Hence, obs does the same :-)
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? Are you planning to pull all of that out into a plugin too? _______________________________________________ compiz mailing list compiz@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/compiz
