Skip to content
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 request] Update timeout settings of all notifications when switching mode #497

Open
itshog opened this issue Feb 9, 2024 · 0 comments

Comments

@itshog
Copy link

itshog commented Feb 9, 2024

I apologize in advance if this has already been requested or if it's somewhat already possible, but, as far as I understand, for each notification mako retains the timeout property from the mode that was active when the notification was originally sent, and not the one from the new mode. So, for instance, having a config like this:

default-timeout=5000

[mode=paused]
invisible=1
default-timeout=0
ignore-timeout=1

will result in every notification sent when the paused mode is active having no timeout even when switching mode, so after exiting the paused mode every notification has to be manually dismissed. Would it be possible to make it so these notifications reset their timeout property to the default-timeout value instead?

My use case for this, as shown with the example above, is having a "don't disturb" mode that hides every notification but disables the timeout, so when I exit this mode I can see the notifications and they are automatically dismissed after the time specified as default-timeout, without having to manually dismiss them. IMO this makes for a nicer and more intuitive behaviour.

I understand that for some users the current behaviour of mako (retaining the timeout settings from the mode active when the notification was sent and never updating them) may be preferable, so maybe this could be made into a user-configurable option (something like retain-timeout=0|1).

Anyway, thanks for the great piece of software!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant