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
With a two screen setup trying to move a window on the second screen from space a to space b results in the window moving to space b + (number of spaces on the first screen).
Basically the spaces on the second screen are indexed starting from 1 again. Moving between spaces still works as usual, i.e. it uses a joint set of indices to refer to spaces on both screens.
(I know this sounds confusing please see my examples below)
This issue popped up for me when I updated to a version of amethyst that uses the new private APIs for moving windows between spaces.
How can it be reproduced?
My setup:
Number of screens: 2
Spaces on first screen: {1,2,3}
Spaces on second screen: {4,5,6,7,8,9,10}
Examples:
Trying to move a window from any space on the second screen to space 1 results in window moving to space 4 = 1+3.
Trying to move a window from any space on the second screen to space 2 results in window moving to space 5 = 2+3
...
Trying to move a window from any space on the second screen to space 7 results in window moving to space 10 = 7+3.
Trying to move a window from any space on the second screen to space 8, 9, 10 results in window not moving.
What applications are involved?
All applications and windows.
Has anything fixed it, even temporarily?
Sadly, no.
The text was updated successfully, but these errors were encountered:
zmheiko
changed the title
Moving windows between spaces on second screen behaves unexpected
Moving windows between spaces on second screen behaves unexpectedly
Dec 23, 2020
System
What's the problem?
With a two screen setup trying to move a window on the second screen from space a to space b results in the window moving to space b + (number of spaces on the first screen).
Basically the spaces on the second screen are indexed starting from 1 again. Moving between spaces still works as usual, i.e. it uses a joint set of indices to refer to spaces on both screens.
(I know this sounds confusing please see my examples below)
This issue popped up for me when I updated to a version of amethyst that uses the new private APIs for moving windows between spaces.
How can it be reproduced?
My setup:
Number of screens: 2
Spaces on first screen: {1,2,3}
Spaces on second screen: {4,5,6,7,8,9,10}
Examples:
Trying to move a window from any space on the second screen to space 1 results in window moving to space 4 = 1+3.
Trying to move a window from any space on the second screen to space 2 results in window moving to space 5 = 2+3
...
Trying to move a window from any space on the second screen to space 7 results in window moving to space 10 = 7+3.
Trying to move a window from any space on the second screen to space 8, 9, 10 results in window not moving.
What applications are involved?
All applications and windows.
Has anything fixed it, even temporarily?
Sadly, no.
The text was updated successfully, but these errors were encountered: