I'm trying to wrap my head around how to document that, but ya I wouldn't mind documenting it. I'll have to think on it.
Chris On Fri, Sep 14, 2012 at 8:40 AM, MokoJumbie <[email protected]> wrote: > Hmm, my initial reaction to that was that it didn't make sense because my > other machines also go to sleep and don't have this behaviour, but then it > hit me. You're right, of course, but with my other machines I only set the > display to sleep, the machine itself is set to never sleep, so of course > the notifications continue to be processed while I am away. > > Since the expected behaviour of the roll-up is that it logs messages while > you are away, can Growl be made to present a notification if the machine is > set to sleep and will prevent notifications from being rolled-up? I imagine > this could behave in a similar way to the screensaver panel when you set > the screensaver delay to a period that is shorter than the display sleep > delay. > > Also, it would be nice if a note was put in the documentation explaining > this behaviour. > > Thanks! > > Nick > . > > > On Friday, September 14, 2012 9:04:51 AM UTC-4, Christopher Forsythe wrote: > >> That sounds like your computer was asleep, it woke up, and then hwg >> noticed all these changes and told you about them. >> >> On Fri, Sep 7, 2012 at 6:31 PM, MokoJumbie <[email protected]> wrote: >> >>> 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]> 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/* >>>>> *ms**g/growldiscuss/-/**zlgsPokgzGEJ<https://groups.google.com/d/msg/growldiscuss/-/zlgsPokgzGEJ> >>>>> . >>>>> To post to this group, send email to [email protected]. >>>>> To unsubscribe from this group, send email to growldiscuss...@** >>>>> googlegroups.**com. >>>>> >>>>> For more options, visit this group at http://groups.google.com/**group >>>>> **/growldiscuss?hl=en<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<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 growldiscuss...@** >>> googlegroups.com. >>> For more options, visit this group at http://groups.google.com/** >>> group/growldiscuss?hl=en<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/-/fPJ42vzJ6mwJ. > > 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. > -- 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 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.
