PIP windows automatically moved under menubar after wake (or reconnecting a virtual screen)

[galoshdin]

Hi!

I want to split a monitor in two. To accomplish that, I :

• created two PIP (associated with the monitor)
• edited the resolution to match what I want (in this case, 1000x1440 and 2440x1440)
• enabled "Above Menu, Dock, Spaces" for both
• enabled "Hide titlebar and controls" for both
• enabled "Start Automatically" for both
• carefully resized and moved them to use the full height of the screen (which is harder that I hoped... I dragged the PIP windows over the OS menu bar and "flush" to a side of the screen. Then, I resized and resized the window using a bottom corner) **

Hopefully, this is giving me a full-height PIP window (or close to it, depending on my precision on that last step). But as soon as I wake the computer from sleep, the PIP windows are moved down and/or resized by 52px (I think). I'm not sure, but it appears to match the height of the system menu bar + the PIP titlebar (which I disabled). If I hit "Reconnect virtual screen" on any screen, all PIP windows are also moved / resized automatically. I think that macOS is doing that to make sure the titlebar is visible after a potential screen change... Ideally, this behaviour shouldn't be applied to a window without a title bar and above everything else like that (or maybe the last known "good" position should be restored after a PIP is created if the macOS thing is unavoidable).

Or maybe I just forgot to enable something... Is there something I can do to "protect" the PIP positions? Or maybe I can achieve what I want (splitting a display in two virtual displays) with something simpler than that PIP nightmare (?)

Other info : This is happening on an Intel MacBook Pro (no notch) with Ventura 13.4.1 connected to an external 3440x1440px display. I tried with both BetterDisplay 2.0.3 Pre-Release (20199) and 1.4.15.

Thanks!

** It might be helpful if PIP windows resizing / moving would snap to the sides of the screens. Right now, resizing using a top corner doesn't allow me to go over the menu bar and moving does not stop me from overshooting (or undershooting) - It takes time and precision to move it to a pixel-perfect corner.

[waydabber]

Yes, the current situation is not ideal in this regard. This will be fully solved when this happens: #197

Hopefully will get there, many PIP/Streaming feature requests are piled up... :) https://github.com/waydabber/BetterDisplay/issues?q=is%3Aopen+label%3APIP%2FStream+sort%3Aupdated-desc

[waydabber]

This should better protect the location of PIP windows from session to session:

#2043
#2080