-
-
Notifications
You must be signed in to change notification settings - Fork 663
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
Custom modules: ability to hide a module? #3341
Comments
It seems this got mistakenly labeled as "clock". Whoever has the ability to change labels may want to fix that. (looks like "update" got mistaken for "date" by the labeler. May be useful to add a whitespace matcher to the regex?) |
I'm not 100% sure I understand it correctly, but when I return {} from a continuous script, the module does disable its event box. Is that not what you want to achieve? E.g. test-output2.sh
test config:
test style:
|
Thanks for elaborating. Can you try #3395 with I should imagine the name of the config option is subject to change if the PR is merged. ;) |
Can confirm provided patch resolves the issue. Thank you! (btw GitHub uses "resolves", "closes" or "fixes" as the magic word that closes a related issue, not "addresses", you might wanna fix that in the PR description) |
I had no idea, thanks. :D |
I have a persistent module that uses JSON output to Waybar. I want it to be able to hide itself when the module thinks it has nothing useful to display — however, after reviewing src/modules/custom.cpp I found no obvious way for a JSON module to hide itself (other than exiting with a non-zero exit code, being restarted and not producing any output — but I would like to avoid that for efficiency reasons).
Possible API design:
{}
hides the module{"display": false}
(a new key) hides the module until a new update arrives where it is unset or set totrue
The text was updated successfully, but these errors were encountered: