Ferdinand Schober

so I got this to work with two scripts like this: (on sway) ----------$HOME/scripts/dmenu-fzf.sh-------------------- #!/bin/bash swaymsg '[title="dmenu-fzf"]' kill || alacritty -t dmenu-fzf -e $HOME/scripts/j4-dmenu-fzf.sh ------------$HOME/scripts/j4-dmenu-fzf.sh---------------------- #!/bin/bash swaymsg '[title="dmenu-fzf"]' kill ||...

Nevermind I just found out about the wrapper part: #!/bin/bash swaymsg '[title="dmenu-fzf"]' kill || alacritty -t dmenu-fzf -e j4-dmenu-desktop --wrapper='swaymsg exec' --dmenu=fzf

I don't quite understand the difference to --wrapper. Right now you would use `alacritty -t dmenu-fzf -e j4-dmenu-desktop --wrapper='swaymsg exec' --dmenu=fzf` with --no-exec you would do `alacritty -t dmenu-fzf -e...

Tested using [LAN Mouse](https://github.com/ferdinandschober/lan-mouse). It's working for me.

This behaviour is the same on KDE.

@emersion could you take a look?

> It occurs to me that we shouldn't even need this new `seat_get_focused_surface` function, we can instead look at `seat->wlr_seat->keyboard_state.focused_surface`. This would handle all cases. I implemented it this way...

Thank you, too!

> I came across this behavior when trying to implement a virtual KVM using `wlr-virtual-pointer-unstable-v1`, `virtual-keyboard-unstable`, `wlr-layer-shell-unstable-v1` and `pointer-constraints-unstable-v1`. Essentially making 1px wide windows on screen borders, detecting pointer enter...

The problem seems to be with swaylock-effects and swaylock-fancy only. The default swaylock works flawlessly