-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
[Feature]: Add APIs to query the inhibitor status of hypridle #71
Comments
Not everything can be reported that way. Hypridle only stores the number of inhibitors, not what they are. To return details about the inhibitors that part of hypridle would need to be totally rewritten. Also for wayland's experimental idle inhibit protocol inhibitors (like the idle inhibit button on waybar), hypridle knows nothing about them. In this case the inhibiting programs talk directly to the compositor (for example hyprland) and that protocol doesn't provide any methods to retrieve the state of the inhibition. Hypridle doesn't know anything about such inhibitors at all, it just stops receiving idle events from the compositor as long as the wayland idle inhibit is active. |
I've been using hypridle and it's been great. However, sometimes it's hard to figure out what's preventing hypridle from working as expected (often due to user error). It would be nice if hypridle could expose some kind of API (file-based or socket-based) so users can query what the current inhibitors are.
Thank you very much!
The text was updated successfully, but these errors were encountered: