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

Dock's transparency is not working when using compositor. #130

Closed
Donskoy-tabak opened this Issue Aug 17, 2014 · 4 comments

Comments

Projects
None yet
3 participants
@Donskoy-tabak

I found one annoying bug: when compositing manager(compton/xcompmgr/etc) and dock(plank/cairo-dock/docky/etc) active simultaneously, instead transpancy area it have black background. This trouble also actual for icewm and uwm. In other wm like openbox, fluxbox, xfwm4, etc docks works fine.

JWM 2.2.2

I noticed that this bug is relevant in wm with integrated taskbar panel. Maybe this bug is in the stack of the taskbar or smth alike.

Icewm bugreport with the same bug:
http://sourceforge.net/p/icewm/mailman/icewm-devel/thread/From_noreply@sourceforge.net_Wed_Feb_27_18:10:15_2013/

Screenshot:
screenshot

Thanks!

@bbidulock

This comment has been minimized.

Show comment
Hide comment
@bbidulock

bbidulock Aug 17, 2014

Contributor

A window manager that supports _NET_WM_OPACITY will read the property from the client window and set it to the same value on the decorative frame to which the window has been reparented so that the composite manager can see the value on the top-level window. JWM does not do this. Nevertheless it is possible to tell you composite manager to treat the dock by res_name and res_class as transparent in the composite manager configuration file and everything will then look fine. It is also possible to tell JWM to set the _NET_WM_OPACITY to a specific value on specific clients by res_name and res_class.

Contributor

bbidulock commented Aug 17, 2014

A window manager that supports _NET_WM_OPACITY will read the property from the client window and set it to the same value on the decorative frame to which the window has been reparented so that the composite manager can see the value on the top-level window. JWM does not do this. Nevertheless it is possible to tell you composite manager to treat the dock by res_name and res_class as transparent in the composite manager configuration file and everything will then look fine. It is also possible to tell JWM to set the _NET_WM_OPACITY to a specific value on specific clients by res_name and res_class.

@joewing

This comment has been minimized.

Show comment
Hide comment
@joewing

joewing Aug 17, 2014

Owner

@Donskoy-tabak, thanks for the bug report and @bbidulock, thanks for the explanation and work around! It sounds like this should be pretty easy to fix, so I'll try to get to it soon.

Owner

joewing commented Aug 17, 2014

@Donskoy-tabak, thanks for the bug report and @bbidulock, thanks for the explanation and work around! It sounds like this should be pretty easy to fix, so I'll try to get to it soon.

@joewing joewing added the bug label Aug 17, 2014

@joewing joewing added this to the Version 2.2.3 milestone Aug 17, 2014

@joewing

This comment has been minimized.

Show comment
Hide comment
@joewing

joewing Sep 5, 2014

Owner

This works for me now, so I'm marking it as closed. Feel free to re-open if there's still a problem.

Owner

joewing commented Sep 5, 2014

This works for me now, so I'm marking it as closed. Feel free to re-open if there's still a problem.

@joewing

This comment has been minimized.

Show comment
Hide comment
@joewing

joewing Aug 27, 2015

Owner

From what I can tell, the problem is that JWM is reparenting the window. These windows do not appear to be setting _NET_WM_WINDOW_OPACITY on the top-level window. I think the correct way to fix this is to avoid reparenting windows that don't want a border or title bar. Unfortunately, this is going to take a bit of development effort to make work.

Owner

joewing commented Aug 27, 2015

From what I can tell, the problem is that JWM is reparenting the window. These windows do not appear to be setting _NET_WM_WINDOW_OPACITY on the top-level window. I think the correct way to fix this is to avoid reparenting windows that don't want a border or title bar. Unfortunately, this is going to take a bit of development effort to make work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment