Dwindle: Moving windows to workspaces does not respect dwindle:force_split

[kolayne]

Bug

Desired behavior

When I move a window to another workspace, I want the window to appear on the new workspace according to dwindle:force_split, rather than according to my cursor location.

Actual behavior

When I move a window to another workspace, if my cursor is in the left part of the screen, the new window appears on the left of the target workspace. This happens regardless of the initial window location (e.g., if my window was on the right but my cursor was on the left, the window will be put in the left of the new workspace) and regardless of whether it is a silent move.

Relevant config options

I tried to configure hyprland such that windows have little to do with cursor position:

dwindle {
        force_split = 2
}

input {
        follow_mouse = 1
        mouse_refocus = false
}

cursor {
        no_warps = true
}

System info

systeminfo.txt

Analysis

The reason for this behavior is the following condition:

Hyprland/src/layout/DwindleLayout.cpp

Line 431 in 36aa465

} else if (*PFORCESPLIT == 0 || !pWindow->m_firstMap) {

, which only respects dwindle:force_split when the window is being mapped for the first time.

Possible solutions

I would like to work on the solution, but I'm not sure what would be the right way to implement it. @vaxerski, should we:

• Just drop the !pWindow->m_firstMap part and always respect dwindle:force_split? (the current documentation does not specify it is only respected on window creation)
• Have a new config value that decides when dwindle:force_split is respected?
• Try to guess this based on other config values, e.g., cursor:no_warps?

[vaxerski]

I always thought that was the desired behavior?

[kolayne]

I don't think so. I want my windows to open on the right and to be moved to the right. The reason is the same: I think left-to-right (old is on the left, new is on the right). The cursor position is irrelevant.

Maybe I got this mindset from using i3, which also always opens new windows in one configured direction.

[vaxerski]

sure, we can make the change then.

[kolayne]

Do you want it as the default behavior? Should there be a new config option?

[Dregu]

smart_split feels like the option that people enable for the behavior you don't want, and it's already handled in this function, so always respecting force_split sounds fine to me without more options to complicate this... And yeah even just the force_split description is pretty clear that only 0 should follow mouse, ever.

[kolayne]

Fixed in #13038