Open LeeThompson opened 5 years ago
This is by design in R5. At the moment, an application can have a maximum of one notification per event class it has registered with Snarl. Subsequent notifications of the same event class will be coalesced into the same notification, and that notification's body text changed to "n new notifications". This is to encourage developers to be more considerate to the end user and to replace or update an existing notification rather than create more each time.
I'm still testing this concept in the 5.1 Betas and it may be that I remove it before 5.1 goes final as it can be a poor UX experience for the user in some circumstances. Interested in your thoughts here.
Also, the R6 OSD engine (see here) will be better suited to notification coalescing, so it may be this feature is pushed out to R6.
My thoughts on it are basically when I get a number of notifications in succession I just see the "x notifications" and there isn't an easy way for me (due to my localhost vs named host problem) to see what they even are so it renders it somewhat useless. (Granted, I use Growl/Snarl mostly for disposable notifications - if I see them great, if not.. that's fine too.)
I use Snarl for new emails notifications, and would like to show separate notifications for each new email. Email client not too smart and can't edit notifications. So, better to have configurable limit, say, 20 notifications in one time, then new replace old ones.
This is a feature Snarl 3.x has where if multiple notifications come in it vertically stacks them.
If 5.x can do this, I haven't figured it out.