Originally created by @nullbyto on GitHub (Oct 25, 2023).
Is your feature request related to a problem? Please describe.
There is a problem when launching apps on Windows, when on a multiple monitor setup.
Whenever an app is launched, it is launched on the last monitor that it was closed on. This is annoying when you need the same app on multiple monitors launched, for example, a terminal or a text editor on each monitor. Every time you would need to go the other monitor to move it to the actual monitor you need.
Describe the solution you'd like
I think a solution would be, to make komorebi move the app after it was launched to the correct monitor, which is focused.
Describe alternatives you've considered
A workaround that worked for me is to use PowerToys, that has a tool named FancyZones that has an option to turn on, to move the newly created window to the current active monitor, as described in this issue: https://github.com/microsoft/PowerToys/issues/8893.
Additional context
To reproduce:
Launch for example: notepad from windows start menu (or PowerToys launcher) on the selected monitor.
It launches every time on the first monitor that it was launching on, even if you go on the second monitor to launch it from there.
If I move the window of the app to the second monitor and then close it, then it launches on the second monitor.
Originally created by @nullbyto on GitHub (Oct 25, 2023).
**Is your feature request related to a problem? Please describe.**
There is a problem when launching apps on `Windows`, when on a `multiple` monitor setup.
Whenever an app is launched, it is launched on the `last monitor` that it was closed on. This is annoying when you need the same app on multiple monitors launched, for example, a terminal or a text editor on each monitor. Every time you would need to go the `other monitor` to move it to the actual monitor you need.
**Describe the solution you'd like**
I think a solution would be, to make `komorebi` move the app after it was launched to the correct monitor, which is focused.
**Describe alternatives you've considered**
A workaround that worked for me is to use `PowerToys`, that has a tool named FancyZones that has an option to turn on, to move the newly created window to the current active monitor, as described in this issue: https://github.com/microsoft/PowerToys/issues/8893.

**Additional context**
To reproduce:
- Launch for example: `notepad` from windows start menu (or PowerToys launcher) on the `selected monitor`.
- It launches every time on the `first monitor` that it was launching on, even if you go on the `second monitor` to launch it from there.
- If I move the window of the app to the `second monitor` and then close it, then it launches on the `second monitor`.
Closing this because I don't believe implementing this is worth the complexity that this introduces into the codebase; if someone is already using a tiling window manager, they should use twm-native options such as workspace_rules or initial_workspace_rules instead of trying to wrangle DWM.
@LGUG2Z commented on GitHub (May 15, 2024):
Closing this because I don't believe implementing this is worth the complexity that this introduces into the codebase; if someone is already using a tiling window manager, they should use twm-native options such as `workspace_rules` or `initial_workspace_rules` instead of trying to wrangle DWM.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @nullbyto on GitHub (Oct 25, 2023).
Is your feature request related to a problem? Please describe.
There is a problem when launching apps on
Windows, when on amultiplemonitor setup.Whenever an app is launched, it is launched on the
last monitorthat it was closed on. This is annoying when you need the same app on multiple monitors launched, for example, a terminal or a text editor on each monitor. Every time you would need to go theother monitorto move it to the actual monitor you need.Describe the solution you'd like
I think a solution would be, to make
komorebimove the app after it was launched to the correct monitor, which is focused.Describe alternatives you've considered

A workaround that worked for me is to use
PowerToys, that has a tool named FancyZones that has an option to turn on, to move the newly created window to the current active monitor, as described in this issue: https://github.com/microsoft/PowerToys/issues/8893.Additional context
To reproduce:
notepadfrom windows start menu (or PowerToys launcher) on theselected monitor.first monitorthat it was launching on, even if you go on thesecond monitorto launch it from there.second monitorand then close it, then it launches on thesecond monitor.@LGUG2Z commented on GitHub (May 15, 2024):
Closing this because I don't believe implementing this is worth the complexity that this introduces into the codebase; if someone is already using a tiling window manager, they should use twm-native options such as
workspace_rulesorinitial_workspace_rulesinstead of trying to wrangle DWM.