[FEAT]: greedy windows #475

Closed
opened 2026-01-05 14:50:57 +01:00 by adam · 1 comment
Owner

Originally created by @BluBloos on GitHub (Sep 28, 2024).

First of all, thank you for this amazing piece of software!

Is your feature request related to a problem? Please describe.

I want the automated part of komorebi to optimize for every window getting the maximum amount of pixels.

Describe the solution you'd like

Let there exist the "allocation event" (AE). this occurs whenever a new window is created, or an existing window is destroyed.
upon AE, "load balance" the windows between all the monitors I have. what I mean by load balance is if I have 2 monitors and 3 windows, but all 3 windows are located on a single monitor, this is not an optimal usage of screen space. I would prefer if there was 1 window on monitor 1, and the other two were on monitor 2.

Originally created by @BluBloos on GitHub (Sep 28, 2024). First of all, thank you for this amazing piece of software! **Is your feature request related to a problem? Please describe.** I want the automated part of komorebi to optimize for every window getting the maximum amount of pixels. **Describe the solution you'd like** Let there exist the "allocation event" (AE). this occurs whenever a new window is created, or an existing window is destroyed. upon AE, "load balance" the windows between all the monitors I have. what I mean by load balance is if I have 2 monitors and 3 windows, but all 3 windows are located on a single monitor, this is not an optimal usage of screen space. I would prefer if there was 1 window on monitor 1, and the other two were on monitor 2.
adam added the enhancement label 2026-01-05 14:50:57 +01:00
adam closed this issue 2026-01-05 14:50:58 +01:00
Author
Owner

@LGUG2Z commented on GitHub (Jan 23, 2025):

This is an interesting idea but I believe it will be better implemented as a separate process which listens to komorebi events and maintains its own state.

@LGUG2Z commented on GitHub (Jan 23, 2025): This is an interesting idea but I believe it will be better implemented as a separate process which listens to komorebi events and maintains its own state.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/komorebi#475