hyprland-conf: follow the pointer, because one now exists
vm-pointer measured what this setting actually does: with follow_mouse=0 Hyprland delivers pointer events only to the keyboard-focused window, so a click aimed at 0.25,0.75 of a session's container put the cursor at x=299 y=519 -- inside that window -- and both clients reported nothing. The click was aimed correctly and delivered nowhere. The comment here said 'no pointer will ever exist; do not let focus depend on one', which was true when written and is false now that the broker injects a virtual pointer. The cursor lease already serialises input, so focus following the pointer cannot make two sessions fight over the keyboard.
This commit is contained in:
1 parent
1c886eec3f
commit
c1dc60af00
1 file changed
+12
-2
+12
-2
@@ -79,8 +79,18 @@ in ''
|
||||
}
|
||||
|
||||
input {
|
||||
# No pointer will ever exist; do not let focus depend on one.
|
||||
follow_mouse = 0
|
||||
# Focus follows the pointer. This was `0`, on the reasoning written here
|
||||
# that no pointer would ever exist — true when it was written, and false
|
||||
# now that the broker injects one.
|
||||
#
|
||||
# It is not a preference. With `0` Hyprland delivers pointer events only to
|
||||
# the keyboard-focused window: measured in `vm-pointer`, a click aimed at
|
||||
# 0.25,0.75 of a session's container placed the cursor at x=299 y=519,
|
||||
# inside that window, and **both** clients reported nothing — the click was
|
||||
# aimed correctly and delivered nowhere. The cursor lease already
|
||||
# serialises input, so letting the pointer move keyboard focus cannot make
|
||||
# two sessions fight over the keyboard.
|
||||
follow_mouse = 1
|
||||
}
|
||||
|
||||
# Frames cost capture bandwidth and CPU, and no one is watching the easing.
|
||||
|
||||
Reference in new issue
Block a user