-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add idle inhibition status in a swaymsg command response #5286
Labels
enhancement
New feature or incremental improvement
Comments
Linking a comment I found related to this #4945 (comment) |
Idle inhibition is tied to surfaces. I think it'd make sense to add idle inhibition status to the |
tardypad
added a commit
to tardypad/sway
that referenced
this issue
May 5, 2020
tardypad
added a commit
to tardypad/sway
that referenced
this issue
May 5, 2020
tardypad
added a commit
to tardypad/sway
that referenced
this issue
May 17, 2020
tardypad
added a commit
to tardypad/sway
that referenced
this issue
May 29, 2020
RedSoxFan
pushed a commit
that referenced
this issue
May 29, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here is my use case: I'd like to display in the status bar whether the idle state is currently inhibited or not (given the current state of the tree).
However, at the moment, the idle info is nowhere to be found in any of the swaymsg command response.
There are several options I could think of to add this info:
Add a new command like
swaymsg -t get_idle_status
or so that would directly return whether it is inhibited as a whole or not.In the get_tree response add a new "inhibit_idle" key for containers that would store a boolean.
Same as previous option but make the "inhibit_idle" key contain any of the possible values ("focus", "fullscreen", "none",...) it was set with.
All those options should make some scripting possible around this idle info.
The text was updated successfully, but these errors were encountered: