So I'm using a laptop which is mostly in dual-monitor (twinview) mode,
but on-the-move is just the single laptop LCD available.
Obviously, if I set rules moving apps to tags[2][1] or similar, this
isn't going to work when using just the laptop without an external
monitor (it doesn't crash, but there's buggy behaviour, as expected).
A 'workaround' is to simply move everything to screen 1, but that's
sub-optimal as well.
>From the default rc.lua I noticed that mouse.screen gets called
sometimes. I could not find that in the reference wiki, but I assumed
it simply refers to the screen the mouse is currently on.
So I have this rule for Firefox (I use role = browser so it only
matches the browser windows and not the password-prompt popup)
{ rule = { role = "browser" },
properties = { tag = tags[mouse.screen][2] } },
It seemed to work at first, but now all the rules which look similar
to the above simply send the apps to screen 2, regardless of where the
mouse is. What's the 'correct' way of doing this? Even better, can I
specify that it would be on screen 2 as long as it exists, but if it
doesn't (screen.count() == 1) just put it on screen 1?
Side note: when changing resolution etc. dynamically (for example,
making the 'left-of' screen in Twinview 'right-of' from
nvidia-settings) awesome still tiles windows to the old resolutions,
leaving a gap. This isn't a big deal though, just reloading works
fine.
--
To unsubscribe, send mail to [email protected].
