Allow Notes to be Stored as History But Not Displayed

[GoogleCodeExporter]

What feature or enhancement do you propose?
Quite simply it would be nice if notes could be disabled (do not display) but 
would still be stored in Growl's history.

What problem does it solve/What benefit does it provide?
For more frequent (or annoying) notes this would allow users to disable the 
notification, but still recap it if they're interested in what may have 
happened, but aren't interested in seeing it.

This is particularly useful for some apps that display relatively banal notes 
where you don't really care for the disruption of seeing it as it happens, but 
it may be nice to recap to ensure that the event *did* occur.

My prime example is Transmission which gives notes when it completes a torrent. 
While I like to know which torrents have been completed, I find the alert 
annoying when it happens, as I have various other cues such as a completion 
sound, dock-badge and so-on already.

Combined with a pulsing menubar widget (issue #316) this provides a way to 
non-intrusively track useful, but not necessarily urgent notices.

Original issue reported on code.google.com by harav...@gmail.com on 16 Oct 2011 at 4:25

[GoogleCodeExporter]

Oh, wanted to add that implementation wise, I actually expected the "Log" 
checkbox to do this. Basically when viewing types of notice for an app in 
Growl, there are currently two options:
[ ] Enabled
[ ] Logging

Now I'm not sure if Logging is actually History related or not, but it 
currently appears to do nothing if a notification is not Enabled. Anyway, I 
think that the Logging state for a notification should also apply to whether or 
not it appears in History.

This you essentially have three notification states:
- Enabled and Logged (default for most common notifications).
- Enabled and not Logged (for time-sensitive notifications where appearing in 
History is superfluous).
- Disable and Logged (for non-urgent informational notifications that are more 
usefully reviewed than seen).

Original comment by harav...@gmail.com on 16 Oct 2011 at 4:31

[GoogleCodeExporter]

logging is history related.

disabled means that growl drops the notification entirely, it won't be logged 
or displayed.

Original comment by rarich...@gmail.com on 25 Oct 2011 at 4:23

[GoogleCodeExporter]

Okay, in that case then the current behaviour is technically flawed (Logging 
should be greyed out if Enabled is unchecked).

However, I think that this shouldn't be the case, the checkboxes should behave 
as they do now, but interdependently, such that logged notes will appear in 
history, regardless of the Enabled setting. This makes sense anyway, as the 
History feature essentially renders actual logging (to Console) irrelevant.

So basically; Enabled would determine whether the note is displayed (or enters 
Rollup), while Logging would determine whether it is stored in History. This 
way you can have either, both, or neither as desired.

Original comment by harav...@gmail.com on 1 Nov 2011 at 12:32

[GoogleCodeExporter]

Original comment by ch...@growl.info on 14 Nov 2011 at 12:43

• Added labels: Product-Growl

[GoogleCodeExporter]

Original comment by ch...@growl.info on 8 Feb 2012 at 3:17

• Added labels: Milestone-Later

[GoogleCodeExporter]

Growl 2.0 adds the ability to disable use of a visual display at the global, 
app, and notification level.  You can leave logging enabled without disabling 
the app (and indeed, it would show up in the rollup if the rollup comes up), 
and/or set other actions as well.  

Original comment by dan...@growl.info on 22 Mar 2012 at 3:32

• Changed state: FixedInSource
• Added labels: Milestone-2.0
• Removed labels: Milestone-Later

[GoogleCodeExporter]

Growl 2 is released, marking these as fixed.

Original comment by ch...@growl.info on 20 Sep 2012 at 3:16

[GoogleCodeExporter]

Original comment by ch...@growl.info on 11 Jan 2013 at 6:27

• Changed state: Fixed