THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Daniel Hahler (blueyed)
Attached to Project - awesome
Summary - Provide context with request::activate signal / separate signal for
_NET_ACTIVE_WINDOW
Task Type - Feature Request
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Low
Priority - Normal
Reported Version - git/master
Due in Version - Undecided
Due Date - Undecided
Details - I would like to handle the `request::activate` signal differently
according to its source / context.
Currently it gets emitted for _NET_ACTIVE_WINDOW and via awful.rules.execute
(for focus=True).
My use case is to not raise/activate Firefox windows by default, but do so if
the request comes via _NET_ACTIVE_WINDOW (when the client/window is activated
via rofi (a window switcher)).
My current workaround is to look at debug.traceback to determine where the
signal is coming from:
local tb = debug.traceback()
if string.find(tb, "awful/rules.lua:%d+: in function 'execute'")
then
-- Signal sent via awful.rules.execute
r = c.type ~= "normal"
else
-- _NET_ACTIVE_WINDOW ewmh request (rofi)
r = true
end
For reference, these are the two possible tracebacks. Basically there's none
for the one being emitted from ewmh.c for _NET_ACTIVE_WINDOW.
stack traceback:
rc.lua:1419: in function <rc.lua:1384>
[C]: in function 'emit_signal'
/usr/local/share/awesome/lib/awful/rules.lua:242: in function 'execute'
/usr/local/share/awesome/lib/awful/rules.lua:193: in function
</usr/local/share/awesome/lib/awful/rules.lua:178> (string)
stack traceback:
rc.lua:1419: in function <rc.lua:1384> (string)
It would be useful to have some context information passed with the signal.
I could imagine also using a dedicated signal for the ewmh request (which would
just emit `request::activate` by default).
More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1264
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.
