THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added:
FS#1171 - Workspace mouse input blocked by transparent layer of Cairo-dock User who did this - Uli Schlachter (psychon) ---------- No, cairo-dock's dependencies scared me enough that I didn't try to reproduce this. You said "clicks do not pass through transparent layer of cairo-dock" which sounds like "cairo-dock is still there, but does some magic to pretend it isn't" which sounds really weird. There must be a window in that area that gets the input and that window must be cairo-dock. In other words, cairo-dock fails at getting its window out of the way and that's cairo-dock's problem. Do you have a bug report or a fix or something like that for fluxbox? "Honor its duty" is quite a generic statement, I would rather hear something more X11-related. I have no idea what bitmap should define some transparency zone and the term "transparency zone" sounds weird and like nothing that is defined in ICCCM and EWMH (these are the relevant standards about what a WM's duty is). You could run xwininfo and/or xprop in a terminal and click on the unresponsive area. That should tell you which window is there and steals input. I bet it will say that the input goes to cairo-dock and I have no idea what that information would tell us. ---------- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1171#comment3651 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to [email protected].
