-
Notifications
You must be signed in to change notification settings - Fork 182
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
[Issue] AGS widgets/menus don't give back focus once closed #502
Comments
facing this same issue. When for example launching sidebar with bind key and you close it with bind key there is no focus on the window. Either i have to move my mouse to bring back focus or switch back and forth in workspaces. Its kind of annoying right now. I am on arch linux with the latest git commit. One more update: if opening any toggle ags widget is closed by pressing escape key then the focus returns but not when pressing the same bind key used to open it. |
Same here. |
click2Close, basically a transparent fullscreen layer to receive clicks, is the cause |
Thanks for the response end-4. Love your work a lotttt! Pls try to find some way if its possible as this situation is kidna annoying as many a times i press the same key to open and close the widget which makes lose focus from window. Then i have to switch workspace or move mouse to bring back focus. Its just itterates after a point. I love all the widgets and config. Hove we find a solution for this. Not sure if i am asking right question but is it possible to use the escape event for like the situation where visible value change, as when pressing escape key to close widget focus comes back again. |
that's exactly how it's implemented i guess i'll have another attempt of filling the screen with eventboxes that close the window on click. this is also what the ags developer recommends |
done easily for overview and cheatsheet |
Thanks a lot man. |
done for sidebar |
prob needs work on hyprland side |
Thanks @end-4 for all your response, i updated to the latest fix and now everything working fine. Now when closing widget focus comes back to window.
I just wanted to ask one question. With the sidebar fix now the animation brings it up from bottom of screen. Is it fixable like the previouse animation or its just the solution for now. I will try to fix it from my side. Still, thanks again for giving us this amazing hyprland config with ags. Love it!!! |
those anims are handled by hyprland
but i don't like it because it makes the layer close animation use the accelerating curve from the enter animation, not the exit one |
this worked, although you are right about the exit animation but i think its still fine as it better then getting the bottom up animation from before. Maybe in future you can fix it. Unitl I will maybe reduce the speed of this animation a little. Rest all good and i think this issue is solved so maybe it can be closed now. Thanks for all the support. |
nah I'm going to leave this open since I'm still not satisfied with the solution |
Also as a That one was fixed as of 5 days ago in hyprwm/Hyprland@7fbe05a |
oops i meant decelerating curve |
The issue
I have been dealing with this issue for quite some time, but only just started looking into it.
Whenever the AGS widgets are opened (e.g the overview on SUPER key or the system panel on SUPER+N), keyboard focus doesn't seem to be returned to the previous window upon closing. The only way I can get it to work again is to go to a different workspace and then switch back to the workspace I wanted to use. I have tried this with different follow_mouse settings but these haven't helped.
If you are focused on for example the terminal (although it's the same for every app), then press SUPER twice (once to open overview and once to close it), the keyboard focus doesn't ever seem to return to the terminal until workspaces are switched and switched back.
I have included my hyprland general config below. I changed some of the focus settings to better suit my needs, but perhaps I've misconfigured something and that could be causing this behaviour (would appreciate if someone attempted to reproduce this issue and that might indicate if it's a me problem or not!).
Click to expand
The text was updated successfully, but these errors were encountered: