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 p
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 C
> 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 vie 02 dic 2011 11:10:49 CLST, Matthew Hague escribió:
{ rule = { class = "Chromium.*" , name = ".*Abrir.*" },
properties = {tag = tags[mouse.screen][2]}}, -- I use it in spanish
I think this will not work as hoped because it chooses mouse.screen when the
rules are loaded, not dynamical
> >{ rule = { class = "Chromium.*" , name = ".*Abrir.*" },
> >properties = {tag = tags[mouse.screen][2]}}, -- I use it in spanish
I think this will not work as hoped because it chooses mouse.screen when the
rules are loaded, not dynamically. My fix for this is to do the following:
{ rule
El 01/12/11 10:14, Tomás Solar Castro escribió:
Hello everyone
I've been working with two screens. So I open, per example, chromium in
screen 1, mod+o to move it to the second screen, and when I fill a form
with a file selector, when I click it, raises an open dialog window, but
not in the secon
Hello everyone
I've been working with two screens. So I open, per example, chromium in
screen 1, mod+o to move it to the second screen, and when I fill a form
with a file selector, when I click it, raises an open dialog window, but
not in the second screen, it is opened in the first screen.