dragging window between monitors on macos is glitchy/laggy

[Kurt-Shiwz]

What Operating System(s) are you seeing this problem on?

macOS

Which Wayland compositor or X11 Window manager(s) are you using?

No response

WezTerm version

20230326-111934-3666303c

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

Yes, and I updated the version box above to show the version of the nightly that I tried

Describe the bug

just use moust move wezterm window between insid-display and Dell display

20230328-162910.mp4

To Reproduce

No response

Configuration

default config

Expected Behavior

No response

Logs

No response

Anything else?

No response

[wez]

This is likely due to the difference in DPI between the monitors. Part-way through the drag, the geometry of the window changes to match the new screen, which interferes with the drag operation.

[snobb]

I've got the same issue on MacOS. Somehow kitty has a solution to that and it works pretty solid. I've done a super ugly workaround which makes window jumpy when you move it between screens (I normally use Rectangle for window operations) but that assumes that the term is always maximised like in my case:

-- ugly workaround for resizing windows when moved between screens.
wezterm.on('window-resized', function(window, pane)
  window:maximize()
end)

Wonder if there is is a way to do it more gracefully. Purely speculating here - have no idea how the GUI works really. Perhaps some pseudo logic like:

if
  window:status == maximised and
  (screen.w != windows.w + padding or
   screen.h != window.h + padding)
then
  window:maximise()
end

Wondering how kitty does it?

This issue and inability to select topmost line because it starts dragging regardless are 2 things that keep me bouncing between kitty and wezterm.
I have config.window_decorations = 'RESIZE' and no tab_bar. But seems like even though the tab_bar is not there, it assumes that it is and starts dragging, when you try selecting the topmost line. Should probably open a separate bug for this.

PS. Thanks for your work on this by the way and keep it up!

[snobb]

Hmm... just tried again and it was fixed somehow - the window stays maximised when moved between screens with different resolutions.

[scoates]

FWIW, this happens to me, but indeed it does only seem to happen when the DPI changes. I have two "big" monitors with the same DPI and I haven't been able to get it to happen when dragging between these two, but it does happen when dragging from a big monitor to the small one (scrollback gets messed up, scroll position is wrong; seems some history is even lost sometimes).

"big" is my two LG monitors; "small" is the built-in Color LCD in the following (not sure where to get the effective DPI/resolution numbers, but I can pull them up if you know where and want them):

Apple M2 Max:

  Chipset Model:	Apple M2 Max
  Type:	GPU
  Bus:	Built-In
  Total Number of Cores:	30
  Vendor:	Apple (0x106b)
  Metal Support:	Metal 3
  Displays:
LG SDQHD:
  Resolution:	2560 x 2880
  UI Looks like:	2560 x 2880 @ 60.00Hz
  Main Display:	Yes
  Mirror:	Off
  Online:	Yes
  Rotation:	Supported
Color LCD:
  Display Type:	Built-in Liquid Retina XDR Display
  Resolution:	3024 x 1964 Retina
  Mirror:	Off
  Online:	Yes
  Automatically Adjust Brightness:	Yes
  Connection Type:	Internal
LG SDQHD:
  Resolution:	2560 x 2880
  UI Looks like:	2560 x 2880 @ 60.00Hz
  Mirror:	Off
  Online:	Yes
  Rotation:	Supported

[snobb]

Hmm... just tried again and it was fixed somehow - the window stays maximised when moved between screens with different resolutions.

Never mind - the issue is still there. Not sure why it could not be reproduced at that moment, but after a while the issue is back and can be reproduced consistently.