-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
missing indicator applet for storing notifications until the user delete it #74
Comments
Seeing as mate-notification-daemon closes after some time of inactivity I don't know how this could be implemented. I guess I could look at xfce4-notifyd. |
Maybe this funcionality should be in an another daemon that would listen to messages passed to a notification daemon? Also, that would work with any daemon as well. Perhaps this funcionality doesn't belong to m-n-d. |
@GiedriusS |
I have some ideas on this. There is existing code I've been testing. Works well enough, I'll post details here next week. |
@raveit65 Maybe it's possible with that but why put it only in mate-notification-daemon when there is a possibility to make a "generic" application? Perhaps this could even be put into an applet where N recent notifications would be shown. I mean this could be implemented by listening on messages sent to /org/freedesktop/Notifications. It's like how you can run |
@flexiondotorg: hmm interesting... |
I've tested the indicator applet for a couple of months, works very well. Check the users code on LP they have various branches for GTK2 and GTK3. Perhaps it could be the basis of something? |
Cool. GTK+2 branch isn't maintained for 2 years though - but as we aim for GTK+3 anyway, I think we can use this indicator with GTK+3 build of |
I'm using the GTK2 version on Ubuntu MATE 15.04 and 15.10, all fine. |
That must be the old version made for Precise and Quantal ( |
I hope you don't want to break the old way of displaying notifications, i get about 200-300 notifications on a day when i'm building packages. Deleting this spam is a mess ;) |
So can we close this? Surely something like this should be implemented as a separate application like the one linked before and not in a notification daemon itself. The application should just listen for calls to org.freedesktop.Notifications and then just put them in a list that is viewable by the user. |
I will change topic to a header which reflect the discussion, than we can leave it open as reminder. Edit: hope new header is fine |
Google Chrome/Chromium removed their own notification centre in favour of systems own notification centres. and as a lot of sites use push notifications (e.g. Facebook, Tweetdeck, Google Products, Pushover...), this would be very important feature to have to not miss anything. |
This is quite important for use cases in which tray icons or somesuch are undesirable, and notifications are used instead. |
This is a vital feature for many people, and the only reason I switch to cinnamon desktop when at work :( |
From https://bugs.debian.org/792577
Dear Upstream,
"I'd suggest to add a functionality to the notification bar - similar to what other DEs such as Xfce and KDE have - so that one can review previous notifications until the user deletes those himself.
The reason for this request is simply that I'm using LinConnect to mirror my Android's notifications i.E. missed calls and SMS to my desktop but whenever I might receive important, it often still gets pass me because MATE by default won't save any notifications.
Possibly this behavior can be changed separtely via a settings window so users can decide what they want to keep and what not. " - Marcos Schnalke
You could implement it here or you could implement it in mate-tweak. This is another user who wants to have the same functionality, if it's feasible.
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/25586858-missing-indicator-applet-for-storing-notifications-until-the-user-delete-it?utm_campaign=plugin&utm_content=tracker%2F1172660&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1172660&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: