THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added:
FS#430 - Java (Swing) dialogs don't go away properly User who did this - Roman Kosenko (kite) ----------
jdk6 does an UnmapWindow on the window which causes an UnmapNotify to be sent to awesome. The problem is that awesome also receives an UnmapNotify if you switch to another tag because it hides windows by unmapping them. So awesome can *NOT* track that signal since it can't tell the difference between those two events.
Why? Awesome know what window it is hiding... so it isn't very big problem to separate true UnmapNotify coming from application and UnmapNotify triggered by awesome request. If you don't want to change anything, at least give to user possibility of dirty hack through lua - send this notify as signal in lua, and user in rc.lua will check if current tag differ from java application's tag and ignore notify in this case, otherwise do c:unmanage(). Maybe this isn't so beautiful solution, but it will help to run java applications under awesome with less work on your side. ---------- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=details&task_id=430#comment2205 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].
