You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the update to 1.10, sway mixed the workspace and put workspace 1 at monitor DP-2, and workspace 2 at monitor DP-1
I've fixed that with adding following:
workspace 1 output DP-1
workspace 2 output DP-2
However, the focus is still wrong, even with setting focus output DP-1, after the initial login, the mouse appears on DP-2
I'm not sure if that information is relevant, but i thougt i'm going to include it.
The real issue is that usually, $drun should open on the focues monitor. $drun is in my case tofi.
If there are no open application this works as expected, if there is kitty open on both monitor, tofi always open on DP-1 - even if kitty on DP-2 is focus. Starting a application would however open it on the right monitor. It's just that tofi is placed wrong.
Interestingly, this is not always the case. Having for example firefox open on DP-2 would also open tofi correctly on DP-2 (if the focus is there). I made some tests:
Another interesting thing is that if i change tofi with something else like spicy - which is another floating app - it seems to work as expected. (but I haven't test too much)
Not sure it the debug logs helps, i've tried to test a few times the behavior while it was running.
Unfortunately this is also a regression of 1.10. There are no issues with 1.9. Please let me know if you need any further information.
The text was updated successfully, but these errors were encountered:
This comment is not helpful. Please refrain from posting such comments (and keep in mind we're all volunteers here).
I am sorry if you didnt find it right, sway is great and I still use it as my daily driver but I will share the whole workflow video please take a look.
Before 1.10 the workspace 1 was my laptop and workspace 2 was my Monitor. When the system would start all my applications would open only on workspace 2 which is my monitor but as u can see its actually mirroring everything i do on both the displays
You can see in the video that i cannot interact with anything on my monitor using the mouse pointer , i have to get the pointer to my laptop screen first and only then i can interact with anything, I only use the defaults sway settings and no custom config for workspaces.
Please fill out the following:
Sway Version:
sway version 1.10
Debug Log:
Configuration File:
Description:
I have a dual monitor setup configured as following:
Since the update to 1.10, sway mixed the workspace and put workspace 1 at monitor
DP-2
, and workspace 2 at monitorDP-1
I've fixed that with adding following:
However, the focus is still wrong, even with setting
focus output DP-1
, after the initial login, the mouse appears onDP-2
I'm not sure if that information is relevant, but i thougt i'm going to include it.
The real issue is that usually,
$drun
should open on the focues monitor.$drun
is in my casetofi
.If there are no open application this works as expected, if there is kitty open on both monitor,
tofi
always open onDP-1
- even if kitty on DP-2 is focus. Starting a application would however open it on the right monitor. It's just that tofi is placed wrong.Interestingly, this is not always the case. Having for example
firefox
open onDP-2
would also opentofi
correctly onDP-2
(if the focus is there). I made some tests:DP-1: empty, DP-2: empty -> tofi always starts on focused monitor (expected behavior)
DP-1: kitty, DP-2: empty -> tofi always starts on focused monitor (expected behavior)
DP-1: empty, DP-2: kitty -> tofi always starts on focused monitor (expected behavior)
DP-1: kitty, DP-2: kitty -> tofi always starts on DP-1
DP-1: kitty, DP-2: firefox -> tofi always starts on focused monitor (expected behavior)
DP-1: kitty, DP-2: pcmanfm-qt -> tofi always starts on DP-1
DP-1: kitty, DP-2: spicy (floating app) -> tofi always starts on DP-1
Another interesting thing is that if i change
tofi
with something else likespicy
- which is another floating app - it seems to work as expected. (but I haven't test too much)Not sure it the debug logs helps, i've tried to test a few times the behavior while it was running.
Unfortunately this is also a regression of 1.10. There are no issues with 1.9. Please let me know if you need any further information.
The text was updated successfully, but these errors were encountered: