[BUG] New Workspace is opened in different screen

[kaolalong]

Describe the bug I have one laptop connected one screen. When I used "supper + 2" to try to open one new workspace, the new Workspace was always opened in the second screen, if there was no app or only 1 app opened. If there were 2 apps opened in the current screen, I use "supper + shift + 2" to move one to 2nd workspace, this new workspace was opened in the current screen. (if you already test with the 1st step, the 2nd workspace may be always in 2nd screen, could use "supper + 3" one time after that and 3rd workspace was opened in 2nd screen also).

To Reproduce Steps to reproduce the behavior:

1. Start laptop with 2 screens connected;
2. at 1st workspace, press "supper + 2", notice the new 2nd workspace is in 2nd screen;
3. move back to 1st workspace and 1st screen, press "supper + 3", notice that new 3rd workspace is in 2nd screen;
4. move back to 1st workspace and 1st screen; open 2 apps; in one app, use "supper + shift + 2", notice that the 2nd workspace is in 1st screen this time.
5. Move back to 1st workspace and 1st screen, press "supper + 5", notice that now 5th workspace is opened in 1st screen now.

Expected behavior Any time, with "supper + number", the new workspace should be opened in current screen.

Screenshots N/A

Distribution (please complete the following information):

• Arch Linux

Additional context With other Hyprland dotfiles setting I used before, there was no this kind problem. But maybe the hyprland build was old. Not sure if this is hyprland problem.

[mylinuxforwork]

@kaolalong Need to setup a similar configuration with my laptop to confirm the issue.

[kaolalong]

@mylinuxforwork Thanks. I found another issue with only one monitor. Not sure if this is the design. Or maybe the same reason with the original one. With 1 monitor, if I opened one app like browser and use "super + 2" to transfer to another workspace, the browser is in 2nd workspace also, which should be "super + shift + 2" action. I could not reproduce this with reboot again. The issue happened was the first reboot after ml4w-hyprland-setup.

[mylinuxforwork]

Please open the issue again if it's still happening.