Open jibbajabber opened 6 years ago
Did you try using a single description for both screens like you have for the Files?
{
name = "www",
init = true,
exclusive = true,
icon = os.getenv("HOME").."/Pictures/awesome/browser.png",
screen = {1,2},
layout = awful.layout.suit.max,
force_screen = true,
class = { "Firefox", "Google-chrome" }
} ,
Awesome 4.2 (dual screen setup) Tyrannical master branch
Launching a new application that has a matched class on multiple tags (on different screens), always ends up on the screen and tag that the application first ran/matched on.
Use case: Start firefox and launch on screen 1 tag 'www' (leave it running). Now focus on screen 2 tag 'www' and launch firefox, firefox is launched on screen 1 tag 'www' despite focus being on screen 2.
I have the following auto start method in my rc.lua
This works as expected and starts among others, a browser on screen 1, tag www.
However, once all auto started clients have launched, if I launch a new client using a mapped key on screen 2:
The new client will always start on screen 1 tag www, this occurs when using either the screen property (commented above) or the tag with screen focused reference. This does not happen without tyrannical.
Tyrannical config:
Strangely this does not happen with the files tag, new nautilus clients are launched on the screen in focus, however new terminator terminals exhibit the same behavior (they are launched on screen 2 tag 'shell'; where auto start launched them)
After looking at issue 83 I added the following to make sure new clients that did not match were handled and added some extra debug to verify screen focus when launching on screen 2:
I added the temporary io writes above for request tag signals to verify the focus was indeed on the screen that launched, the following logs confirmed that the focus was indeed the desired screen: