Then I guess I don't understand how the rollup addresses this issue at all?
On Feb 24, 6:54 pm, Chris Forsythe <[email protected]> wrote: > Regular notifications should show up and then go away. If you're gone for > hours and come back, you should have the rollup and not all of notifications > filling up your screen. There are some exceptions to that I believe, i'd have > to look into it again to remember those. > > -- > Chris Forsythe > > > > > > > > On Friday, February 24, 2012 at 5:25 PM, Devin wrote: > > Sorry, I may be missing something, but are you implying the the > > regular notifications shouldn't be still coming up when the rollup is > > displayed? Because for me, they still keep coming. > > > On Feb 17, 10:42 am, Chris Forsythe <[email protected] (http://growl.info)> > > wrote: > > > We implemented the Rollup feature to address this issue. Do you have that > > > disabled? > > > > -- > > > Chris Forsythe > > > > On Friday, February 17, 2012 at 2:53 AM, kasakka wrote: > > > > I think this would be essential to implement in Growl. Every day when > > > > I wake my computer from sleep I get my whole screen filled with > > > > messages from the Linkinus IRC client as it loads the playback buffer > > > > of my IRC bouncer. The app is working as expected as it interprets the > > > > bouncer playback buffer as hundreds of new messages. Yes, I've asked > > > > the developers to implement a notification flood protection but so far > > > > nothing has been done. > > > > > However, this is primarily a Growl issue. It would allow a malicious > > > > app for example to constantly fill the screen with messages unless the > > > > user quits the app, quits Growl or kills the GrowlHelperApp. There is > > > > no situation where filling the display with tens of messages, making > > > > everything else impossible, would be useful. > > > > > So I propose the following: > > > > > 1. Add a global "maximum number of notifications on screen at once" > > > > setting. Anything more than this gets simply dropped or Growl waits x > > > > amount of time to display them, essentially queuing the notifications > > > > (user option which way to use). > > > > 2. Add an application specific limit so you can force applications > > > > that might give lots of notifications to only be able to churn out x > > > > amount. > > > > > Shouldn't be too difficult to implement. > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "Growl Discuss" group. > > > > To post to this group, send email to [email protected] > > > > (mailto:[email protected]). > > > > To unsubscribe from this group, send email to > > > > [email protected] > > > > (mailto:[email protected]). > > > > For more options, visit this group > > > > athttp://groups.google.com/group/growldiscuss?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Growl Discuss" group. > > To post to this group, send email to [email protected] > > (mailto:[email protected]). > > To unsubscribe from this group, send email to > > [email protected] > > (mailto:[email protected]). > > For more options, visit this group > > athttp://groups.google.com/group/growldiscuss?hl=en. -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
