Closed albfan closed 5 years ago
I guess this is in wayland, right? It can be that gnome-terminal bypasses X11 entirely, and thus doesn't actually generate events screenkey can see.
Yes it is. Migrate to gtk3 would solve it? Why chrome do not capture input, neither other apps. What's the difference.
I can do a triage if you know a battery of apps to try with, is there any terminator that should work?
On Thu, Dec 21 2017, Alberto Fanjul wrote:
Yes it is. Migrate to gtk3 would solve it? Why chrome do not capture input, neither other apps. What's the difference.
I don't know the situation exactly, as I'm not going to try wayland until I have a decent tiling window manager and server-side-decorations everywhere, but it's unlikely this is ever going to work.
wayland has a different input model, and the inputlistener in screenkey probably needs to be rewritten completely.
I'm not even sure server-side full input capture can actually be done in wayland in the current state (I'd be happy to be proven wrong).
Will ask on GNOME forums for this, meanwhile:
Using x11 it works correctly
Open gnome-terminal or terminator all the input goes to that windows, and nothing goes to screenkey
If you change to focus a browser or other kind of app, input goes again to screenkey