Open Kasper24 opened 3 years ago
This sounds like a duplicate of #3349.
Sorry, but I only have the same answer to give (and it's still unacceptable): I can't reproduce this issue, it works as expected on my machine.
Uuuh! With some searches, I found #2149 :
hm... I guess this either never worked, or is broken ever since awesome became a reparenting WM. I do not see this being fixed any time soon, sorry (even though that would certainly be possible, but would also mean that each motion event needs a round-trip through the WM before being sent to the client, i.e. something that could cause lag).
So, now I can't explain why it's working on my machine... But it seems it's intended that the event works only on the window decoration (titlebars).
@Aire-One
As I said, I already tried the suggested fix to no avail.
But it seems it's intended that the event works only on the window decoration (titlebars).
Is it? mouse::enter gets called anywhere, clients or titlebars, so I'd think the same should apply to moues::move? maybe the naming should be updated as it's somewhat confusing?
Ran into this today, I assume @psychon is right here. Anyway, if someone has a solution for a reliable "focus follows mouse" implementation, let me know :)
Output of
awesome --version
:awesome v4.3-1058-g906dc543e (Too long) • Compiled against Lua 5.3.6 (running with Lua 5.3) • API level: 4 • D-Bus support: yes • xcb-errors support: no • execinfo support: yes • xcb-randr version: 1.6 • LGI version: 0.9.2 • Transparency enabled: yes • Custom search paths: no
How to reproduce the issue:
Add this code:
Actual result:
mouse::move on the client only gets called when moving the mouse on the titlebar
Expected result:
I want to use it for sloppy focus. It should get called when I move the mouse on the actual client, not just the titlebars, at least I'd think so.