i tried your hack, but it the open file window is still raising at
the first screen :(
Ah. I just tested my setup with two screens and Chromium, and the open file
dialog comes up fine on mouse.screen. Maybe you could post your rules
applying to Chromium -- could be something interfering?
El 07/12/11 07:35, Matthew Hague escribió:
i tried your hack, but it the open file window is still raising at
the first screen :(
Ah. I just tested my setup with two screens and Chromium, and the open file
dialog comes up fine on mouse.screen. Maybe you could post your rules
applying to
On Wed, 7 Dec 2011, Tomás Solar Castro wrote:
-- { rule = { class = Chromium , instance = chromium },
-- properties = {tag = tags[mouse.screen][2]}},
This is mouse.screen at the time awesome was started. What you want is a
callback rule tagging the client. Your mouse.screen will be
Hello Awesome developers,
I've implemented a patch on top of the 3.4 branch (I could not test on
master, because I couldn't get Awesome running with the awesomerc.lua
in the repository). This patch allows you to use a string key name for
root.fake_input as opposed to a numerical key code. My
