-
Notifications
You must be signed in to change notification settings - Fork 597
-
Notifications
You must be signed in to change notification settings - Fork 597
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
setting client.screen doesn't properly change client.active #3826
Comments
I could make a pull request to simply change this function to make it work as it should, but I'm not sure if there is some other underlying issue that should be fixed instead, so I figured I should make this first. |
Okay, so after some testing. It seems that the problem might actually be with self:emit_signal. It seems to be that the client does actually unfocus, but that the signal is somehow only emitted before that, when it should be emitted after. Is there a way to emit a signal on the next event loop rather than on the current one?
|
Haven't really looked too much into the bug in the OP but:
Take a look at gears.timer.delayed_call |
You might want to take another look at its documentation yourself. It does not do what Pikabyte is asking for. |
Output of
awesome --version
:awesome v4.3-1588-g11f5eff3 (Too long)
• Compiled against Lua 5.4.4 (running with 0.9.2)
• API level: 4
• D-Bus support: yes
• xcb-errors support: no
• execinfo support: yes
• xcb-randr version: 1.6
• LGI version: /usr/share/lua/5.4/lgi/version.lua
• Transparency enabled: yes
• Custom search paths: no
How to reproduce the issue:
Simply change a client to a new screen, and look at if the client is active before and afterwords. (Assume "1" is a different screen in the code)
Actual result:
You'll notice that the output suggests client says it is active, but will actually not be.
Expected result:
The expected result should be that the client should not be active. This expectation comes from the code for client:move_to_screen, where it seems to assume it works like this. It sends an activate request which does nothing because the client already thinks it's active.
The text was updated successfully, but these errors were encountered: