Focus stuck on wrong monitor after boot

[Me-Phew]

Is there a way to set which monitor (or workspace) is focused on plugin startup?

With the setup below I end up with my secondary monitor (DP-3, which would be workspace 11 in this case) focused initially after boot.

Removing plugin reload (exec-once = hyprpm reload -n) makes the focus stay on the primary monitor (DP-1, workspace 1) after boot even without any dispatch commands.

monitor=DP-1, 2560x1440@164.96, 1920x0, 1
monitor=DP-3, 1920x1080@74.00, 0x0, 1

plugin {
    split-monitor-workspaces {
        count = 10
        keep_focused = 1
        enable_notifications = 1
        enable_persistent_workspaces = 1
        enable_wrapping = 1
    }
}

exec-once = hyprpm reload -n
exec-once = hyprctl dispatch focusmonitor DP-1 # Does nothing
exec-once = hyprctl dispatch workspace 1 # Also nothing

[zjeffer]

With the setup below I end up with my secondary monitor (DP-3, which would be workspace 11 in this case) focused initially after boot.

The reason it does this is because at plugin startup, we loop over every monitor and ensure the focus is set to the first workspace on that monitor. The monitor with the highest ID (your second monitor) is last, so that's why focus ends up there.

I'll see if I can improve that behaviour.

---

exec-once = hyprctl dispatch focusmonitor DP-1 # Does nothing
exec-once = hyprctl dispatch workspace 1 # Also nothing

The reason this does nothing is because of a race condition: the reload call loads the plugin asynchronously so by the time it gets to creating the workspaces, it has already executed the above two commands. The plugin creates and focuses the workspaces after that.

I might also add an option to the plugin to allow the user to choose a monitor (based on id, output or description) that should be focused after we loop over all monitors.

[zjeffer]

#209

[Insprill]

I've had this same issue for a while, which I fixed by dispatching focusmonitor 0.75 seconds after reloading plugins in exec-once. #209 doesn't allow me to remove that, since what Hyprland considers my first monitor is actually my second.

Hyprland already has a cursor:default_monitor config option (docs) which sets what monitor the cursor should focus on after startup. Can this plugin simply read that option and focus that monitor, falling back to the behaviour in #209 if it isn't set?

[zjeffer]

Hyprland already has a cursor:default_monitor config option (docs) which sets what monitor the cursor should focus on after startup. Can this plugin simply read that option and focus that monitor, falling back to the behaviour in #209 if it isn't set?

This is very interesting, I'll look into adding this (or someone else can do it if they're faster), it sounds like a pretty easy addition.

[zjeffer]

@Insprill @Me-Phew Can you test #219?

[Me-Phew]

I've just tested #219 and it seems to be working fine.

[Insprill]

Just updated, and it indeed works. Thank you :)