Is there a way to block binds from going to the application

[carbolymer]

I'm trying to implement mouse scroll zoom with binds. I have something like this:

binde = $mainMod, mouse_down, exec, hyprctl keyword cursor:zoom_factor $(hyprctl getoption cursor:zoom_factor | awk '/^float.*/ {print $2 + 0.5}')    
binde = $mainMod, mouse_up, exec, hyprctl keyword cursor:zoom_factor $(hyprctl getoption cursor:zoom_factor | awk '/^float.*/ {print $2 - 0.5}')    

But when I trigger the bind by scrolling over an application window, like firefox, the bind gets executed correctly, but the browser page scrolls as well.

Is there a way to prevent firefox from seeing the scroll event in such case?

[vaxerski]

they should be eaten, you can open a bug report

[carbolymer]

#9319

[RayJameson]

the issue above was closed because of moving to discussions, but this problem is still relevant, if I scroll mouse + mod, it zoom in once and then input is passed through to the application

[RayJameson]

nevermind, setting this option fixed it, it would be nice to mention it on the wiki page

binds {
    scroll_event_delay = 0
}

[RayJameson]

I opened a PR for this change hyprwm/hyprland-wiki#1059

[jerhos]

This is still more of a bandaid solution. Yes, it solves the problem here. But only if you exclusively use mouse_down/mouse_up in non-timing-sensitive shortcuts. E.g. setting scroll_event_delay = 0 messes with scrolling through workspaces.

Try using

binds {
  scroll_event_delay = 0
}

# Zoom screen using mouse
binde = $mainMod, mouse_down, exec, hyprctl keyword cursor:zoom_factor $(hyprctl getoption cursor:zoom_factor | awk '/^float.*/ {print $2 + 0.5}')    
binde = $mainMod, mouse_up, exec, hyprctl keyword cursor:zoom_factor $(hyprctl getoption cursor:zoom_factor | awk '/^float.*/ {print $2 - 0.5}')  

# Scroll through workspaces using mouse
bind = $mainMod+alt, mouse_down, workspace, r-1
bind = $mainMod+alt, mouse_up, workspace, r+1

and you'll find out that you now scroll through 5-10 workspaces in one go. The delay is needed here to stop you from skipping. Incidentally workspace suffers from the same passthrough problem when a delay is set. It's just less noticable due to the nature of it.