That's just it. It does seem fairly straightforward, but because it it giving me unexpected behaviour I had to refer to the docs to see if there is a preference to change the behaviour, only to find that they don't reflect the current state of the app.
To clarify, I'll use an example. I am running hardwaregrowler on a corporate network. If I leave my computer on and go away for a day, I would expect that all notifications would be logged according to my preferences as well as redirected to the rollup. This is all happening as expected. However, when I return to work the next day, wake my screen and dismiss my screensaver, all the notifications which were logged and sent the screen immediately as though the events happened at that immediate moment, resulting in possibly over 100 notifications. It might be worth noting that these do not fade out. I have to roll over them to dismiss them. On Wednesday, September 5, 2012 10:50:13 AM UTC-4, Christopher Forsythe wrote: > > There aren't that many questions to answer about rollup, hence the lack of > documentation about it. It should be pretty obvious as to what it does, > which is to send every notification to Rollup based on the configuration. > > Can you explain a bit more about your last sentence? > > Chris > > On Wed, Sep 5, 2012 at 9:47 AM, MokoJumbie <[email protected]<javascript:> > > wrote: > >> Can someone please update the docs on the growl web site? They are out of >> date and there is no info on the Roll-up preference pane. >> >> As I understand it, the roll-up is meant to group all your notifications >> in a single window after a given idle time, and that this is done to reduce >> the potential clutter that would build up when coming back from idling. >> >> In my case, the roll-up is working as expected, except that all my >> notifications are deferred until I come back, where they snowball onto my >> screen. I can't find a way to prevent this behaviour. Any thoughts? >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Growl Discuss" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/growldiscuss/-/zlgsPokgzGEJ. >> To post to this group, send email to [email protected]<javascript:> >> . >> To unsubscribe from this group, send email to >> [email protected] <javascript:>. >> For more options, visit this group at >> http://groups.google.com/group/growldiscuss?hl=en. >> > > > > -- > Chris Forsythe > @The_Tick <http://twitter.com/The_Tick> > > -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/growldiscuss/-/4rQW5JAgQxAJ. 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.
