Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Toggle Tiling" shortcut puts windows in random positions #1652

Open
Andrew15-5 opened this issue Sep 3, 2023 · 1 comment
Open

"Toggle Tiling" shortcut puts windows in random positions #1652

Andrew15-5 opened this issue Sep 3, 2023 · 1 comment

Comments

@Andrew15-5
Copy link

(1) Issue/Bug Description:

I want to open viewer on the left and editor on the right every time. When I enable tiling windows mode, the 2 windows can be in 1 of the 2 possible positions, and it is completely random! It doesn't matter which window was opened first, is currently in focus, where they are located — nothing! Both windows are always at the exact same position with the same geometry, because they are created from the script.

(2) Steps to reproduce (if you know):

  1. open 2 windows on the same virtual desktop
  2. put the one that you want to be on the left side (L) to the left
  3. put the one that you want to be on the right side (R) to the right
  4. enable window tiling mode
    The (L) window could be on the left or on the right side, and the (R) window also can be in one of the 2 positions, and it's completely random.

Here are 2 windows on a desktop that are specifically moved to the left and right sides (which doesn't help!):

screenshot_2023-09-03_17-10-36

Sometime I will get this result:

screenshot_2023-09-03_17-11-11

And sometime I will get this result:

screenshot_2023-09-03_17-12-25

(3) Expected behavior:

Windows that have the exact same position and geometry must always go to the same position in tiling mode every single time.

(4) Distribution (run cat /etc/os-release):

NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
LOGO=distributor-logo-pop-os

(5) Gnome Shell version: 42.5

(6) Pop Shell version:

pop-shell:
  Installed: 1.1.0~1682616779~22.04~b5accce
  Candidate: 1.1.0~1682616779~22.04~b5accce
  Version table:
 *** 1.1.0~1682616779~22.04~b5accce 1001
       1001 http://apt.pop-os.org/release jammy/main amd64 Packages
       1001 http://apt.pop-os.org/release jammy/main i386 Packages
        100 /var/lib/dpkg/status

(7) Where was Pop Shell installed from: Official ISO file

(8) Monitor Setup: 1080p

(9) Other Installed/Enabled Extensions: only some built-in ones

(10) Other Notes:

Sometimes tiling mode can be useful, but since I can't determine where the windows will be placed, it makes it unusable if you rely on the auto tiling (initial) positioning. I want to run script and start typing on the right side right away, but with this bug I have to use Super+Enter, l, Enter to swap window positions. This is very annoying.

P.S. When enabling tiling mode and I have windows on many virtual desktops, then there is also a 50/50 chance of windows randomly jumping/switching virtual desktops. And windows from the same desktop could end up on different desktops. This breaks my workflow all the time! Why place specific windows on specific desktops, if after tiling mode they can be shuffled like a card deck (without permission)?

@Andrew15-5
Copy link
Author

I don't know if there are even some documented rules on how exactly auto tiling determines where every window should go, but if there is one, please share the link to the rules. I only found "you can do this with this shortcut, and that with that shortcut" type of information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant