[BUG] UW Screen with apps in center and Left/Right window fill not working

[maxipallotto]

So I have a UW Samsung monitor

BUG: I configured slack and WhatsApp in the middle of the display and I am trying to use Fill Left or Fill Rightwith Chrome and it completely ignores the apps in the center, overlapping them randomly.

Expected behaviour: Fill left or right portion of the display left by the apps already taking the middle of display, without overlapping them.

Video:
https://github.com/user-attachments/assets/57ac0ffe-720e-4877-852c-8480dba0088f

Logs:
2026-08-14T11:09:29-03:00: AX sizing proposed: (3126.0, 1440.0), result: (3126.0, 1440.0)
2026-08-14T11:09:29-03:00: AX position proposed: (-1713.0, -1440.0), result: (-1713.0, -1440.0)
2026-08-14T11:09:29-03:00: AX sizing proposed: (3126.0, 1440.0), result: (3126.0, 1440.0)
2026-08-14T11:09:29-03:00: [fillLeft], display: (-1713.0, 1107.0, 5120.0, 1440.0), calculatedRect: (-1713.0, -1440.0, 3126.0, 1440.0), resultRect: (-1713.0, -1440.0, 3126.0, 1440.0), srcScreen: C49RG9x, destScreen: C49RG9x, resultScreen: C49RG9x
2026-08-14T11:09:34-03:00: AX sizing proposed: (2560.0, 1440.0), result: (2560.0, 1440.0)
2026-08-14T11:09:34-03:00: AX position proposed: (-1713.0, -1440.0), result: (-1713.0, -1440.0)
2026-08-14T11:09:34-03:00: AX sizing proposed: (2560.0, 1440.0), result: (2560.0, 1440.0)
2026-08-14T11:09:34-03:00: [fillLeft], display: (-1713.0, 1107.0, 5120.0, 1440.0), calculatedRect: (-1713.0, -1440.0, 2560.0, 1440.0), resultRect: (-1713.0, -1440.0, 2560.0, 1440.0), srcScreen: C49RG9x, destScreen: C49RG9x, resultScreen: C49RG9x
2026-08-14T11:09:42-03:00: AX sizing proposed: (2982.0, 1440.0), result: (1994.0, 1440.0)
2026-08-14T11:09:42-03:00: AX position proposed: (425.0, -1440.0), result: (425.0, -1440.0)
2026-08-14T11:09:42-03:00: AX sizing proposed: (2982.0, 1440.0), result: (2982.0, 1440.0)
2026-08-14T11:09:42-03:00: [fillRight], display: (-1713.0, 1107.0, 5120.0, 1440.0), calculatedRect: (425.0, -1440.0, 2982.0, 1440.0), resultRect: (425.0, -1440.0, 2982.0, 1440.0), srcScreen: C49RG9x, destScreen: C49RG9x, resultScreen: C49RG9x
2026-08-14T11:09:47-03:00: AX sizing proposed: (2982.0, 1440.0), result: (2015.0, 1440.0)
2026-08-14T11:09:47-03:00: AX position proposed: (425.0, -1440.0), result: (425.0, -1440.0)
2026-08-14T11:09:47-03:00: AX sizing proposed: (2982.0, 1440.0), result: (2982.0, 1440.0)
2026-08-14T11:09:47-03:00: [fillRight], display: (-1713.0, 1107.0, 5120.0, 1440.0), calculatedRect: (425.0, -1440.0, 2982.0, 1440.0), resultRect: (425.0, -1440.0, 2982.0, 1440.0), srcScreen: C49RG9x, destScreen: C49RG9x, resultScreen: C49RG9x
2026-08-14T11:09:50-03:00: AX sizing proposed: (2560.0, 1440.0), result: (2560.0, 1440.0)
2026-08-14T11:09:50-03:00: AX position proposed: (847.0, -1440.0), result: (847.0, -1440.0)
2026-08-14T11:09:50-03:00: AX sizing proposed: (2560.0, 1440.0), result: (2560.0, 1440.0)
2026-08-14T11:09:50-03:00: [fillRight], display: (-1713.0, 1107.0, 5120.0, 1440.0), calculatedRect: (847.0, -1440.0, 2560.0, 1440.0), resultRect: (847.0, -1440.0, 2560.0, 1440.0), srcScreen: C49RG9x, destScreen: C49RG9x, resultScreen: C49RG9x
2026-08-14T11:11:04-03:00: Stopping cursor tracking (menu open: true, stashed count: 0)
2026-08-14T11:11:13-03:00: Stopping cursor tracking (menu open: false, stashed count: 0)
2026-08-14T11:12:08-03:00: Unable to find app bundle for com.apple.automator.xpc.runner
2026-08-14T11:12:46-03:00: Failed to find frontmost window.

[rxhanson]

Thanks for the detailed report! Right now, the fill algorithm takes into account the frontmost windows on first execution and will cycle through windows to fill next to on subsequent executions. In looking at your scenario, perhaps the first iteration should be filling empty space and following iterations should catch the other scenarios. I’ll try some things out.

[maxipallotto]

Hi Ryan!
Any news on this?
Regarding your comment: My take is that the user ALWAYS expects the fill command to use all EMPTY space... I can't think of a use for the other scenarios but you're the expert here.

[rxhanson]

Thanks for checking in! I haven't gotten to it yet, but I have it slated for this release that I'm currently working on.

The reason it works the way it currently does is because I built it so that I could simply keep hitting the fill shortcut multiple times to cycle through the different windows that it fills against (cycling to 1/2 if there's not a window found to fill against), as I typically have several layers of windows. I appreciate your feedback on this, since your scenario certainly makes sense and is likely common.