THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#848 - Different handling of _NET_ACTIVE_WINDOW?
User who did this - Uli Schlachter (psychon)
Reason for closing: Fixed
Additional comments about closing: commit
04dee81d135bf630368bd2c5aef126b3f7b35cd1
Author: Uli Schlachter <psyc...@znc.in>
Date: Thu Mar 6 17:47:55 2014 +0100
client: Add request::activate signal (FS#848)
When we receive a _NET_ACTIVE_WINDOW request on the root window, we used to
just
focus and raise the window. This didn't do much for clients which are on
non-selected tags.
Thus, this commit makes awesome emit request::activate on the client
instead.
This is used in awful.ewmh to implement the old behavior again, but with
additionally marking the client as urgent if it isn't visible.
People who don't like this behavior can use client.disconnect_signal to
disable
this behavior again. To make this really possible, awful.ewmh becomes a
"non-nil" module.
Signed-off-by: Uli Schlachter <psyc...@znc.in>
More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=848
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 awesome-devel-unsubscr...@naquadah.org.
