When you switch spaces and return, you may find that a window that was previously tiled is now floating.
This also appears in the window switcher, and Tangrid’s management is functioning properly.
However, even if I switch the problematic window back to tiled mode and then open a new window, it does not split properly.
This issue began occurring in version 1.5.6 and is still occurring in 1.5.7.
I would like to submit the logs, but I’m hesitant because they contain the window titles.
1.5.7 Switching spaces may cause the tiling to break
Replies11
Logs would help me pinpoint the issue much faster.
You can clear the old logs, then reproduce a minimal bug scenario so the logs only contain what's relevant to the bug.
Log directory: ~/Library/Application Support/Tangrid/Logs
Prob duplicate of https://discord.com/channels/1221772275997474816/1536535581247668334
I'm indeed still seeing this phenomenon after 1.5.7
Did you use any fillScreen-related functionality while this bug was occurring?
I'm not sure what "fillScreen" means here.
my basic repro loop is:
- have a single window app A active on an otherwise empty space
- if needed, cmd drag to tile the window
- cmd-tab to single window app B which is on another, also other empty space
- if needed, cmd drag to tile that window
Then, i keep cmd-tabbing between both app (which triggers a change of space).
Expected: both window keep tiled (and thus use the full screen)
Actual: both window appear untiled, sized to an oddly specific smaller size (~50% surface)
No amount of cmd-dragging-to-tile fixes the situation.
Actually it's weird. When I get in this loop, if I leave window B in its untiled-smaller-size state, then window A remains properly maxed-tiled and can observe steady state when cmd-tabbing between the two. But the moment i cmd-drag window B back to tiled-maxed and then cmd-tab, I'll find window A in the untiled-smaller-size state.
Bi-stable thing going on.
Thanks for these details
I believe the “fillScreen” feature temporarily maximizes one of the split windows, and I use it quite often.
There have been some bugs from the recent fillScreen changes, working on it now.
v1.5.8 updated
It seems the problem has been resolved.