A window moved across screens must be re-adapted
Aliases: window change of display · display-change reflow · cross-monitor window
What it is
When a window is dragged onto another display, the destination is a different physical environment: different size, and a different apparent scale and color. Cross-display re-adaptation means the window recomputes itself at the moment of the change—whether it still fits, whether its panes still stand, whether menus and tools remain inside that screen’s visible area. Following the pointer’s coordinates is not the claim.
A layout that had just fit on the source screen may overflow on the neighbor, look undersized, or leave the primary action off-screen. Changing displays is a change of environment, not a translation.
Why it happens
An extended desktop stitches screens into one large coordinate plane, but the stitch is not a visual continuum—there is a bezel, a gap, sometimes a dead band. In Hutchings’s diaries, moving a window across that seam is ordinary, and people treat it as changing benches rather than sliding across one table. On arrival, the client area’s ratio to that screen has changed: three panes that filled a 14-inch laptop clip a column on a smaller portrait external; dragged the other way, a single pane leaves a hole that looks like missing content.
Apparent size and color also jump at the bezel, as if the object were swapped. If the app still paints under the source screen’s constraints, the new screen clips, shows an oversized blank, or opens satellite windows on the old coordinate system. Adaptation belongs at the moment the window’s centre (or title bar) now belongs to a different display, not at the next manual resize.
Studying it
Field diaries record how often windows cross the seam and what adjustment happens immediately after (maximize, change the split, drag it back). Lab tasks drag the same window from display A to B and compare “keep the source layout” against “reflow for the destination.”
Independent variables: size relationship of the two screens, layout complexity on the source, whether reflow runs on the crossing. Dependent variables: first corrective action after the crossing, overflow or empty-pane incidents, duration of the interruption.
Setting both screens identical measures away the need to adapt. The real condition is a laptop plus a different external.
Where it stops holding
Mirror mode has no second environment; cross-display adaptation does not arise. A window deliberately stretched into a super-wide rectangle that spans both screens has no single destination; the rule has to become an explicit “which screen do we follow,” or a refusal to maximize across the seam. Exclusive fullscreen usually enters fullscreen anew on the destination rather than translating a layout. In remote desktop, the guest’s “screens” and the local “screens” are not the same topology, and the crossing semantics slip again.
Applying it
- When a window’s owning display changes, recompute for the destination: drop a column or collapse a secondary pane if it no longer fits; if it grew, do not leave a hole that looks like a load failure.
- Satellite windows (inspectors, palettes) follow the main window across the seam; do not leave them at the source coordinates.
- Verify by dragging the main window from the laptop to the external and back. After each release, complete one step of the current task. If the next move is a manual resize or a hunt for a missing panel, the crossing did not finish adapting.