Timestamps in notifications

[GoogleCodeExporter]

What feature or enhancement do you propose?
Displays should show (or otherwise include) the date and time a notification 
was received by Growl.

What problem does it solve/What benefit does it provide?
In the case of a sticky notification, knowing when the notification was 
received would tell the user how long the notification has been on the screen. 
Information that was time-sensitive may no longer be pertinent; knowing when 
Growl received it would enable the user to know whether it is still pertinent.

Original issue reported on code.google.com by p...@growl.info on 27 Apr 2011 at 4:50

[GoogleCodeExporter]

Not yet decided: If we do this, should it be a per-display option, a 
per-notification option, or both?

Original comment by p...@growl.info on 27 Apr 2011 at 4:51

[GoogleCodeExporter]

My thought is: If we do this, let's make it automatic in visual displays and 
automatically shown only on sticky notifications. No separate options.

Users: If you want a separate option, please explain why you would need a 
timestamp on a non-sticky notification.

Original comment by p...@growl.info on 27 Apr 2011 at 4:53

[GoogleCodeExporter]

Relevant discuss group threads (latest first, but otherwise not in any 
particular order):

http://groups.google.com/group/growldiscuss/t/e5f3579ff78407d8
http://groups.google.com/group/growldiscuss/t/1545df42d1c67a32
http://groups.google.com/group/growldiscuss/t/32f8b82d321ed99a
http://groups.google.com/group/growldiscuss/t/3e93e37ca9142137
http://groups.google.com/group/growldiscuss/t/9cf03879b12e0587
http://groups.google.com/group/growldiscuss/t/c1ec882a4be71f09

Original comment by p...@growl.info on 27 Apr 2011 at 5:04

[GoogleCodeExporter]

“Users: If you want a separate option, please explain why you would need a 
timestamp on a non-sticky notification.”

Or, conversely, your case in which having a timestamp on a sticky notification 
is a bad thing.

Original comment by p...@growl.info on 27 Apr 2011 at 5:06

[GoogleCodeExporter]

rjt says[1]:

“““
Analyzing my use of sticky notifications, I realize that each and every
time I come back to one on my screen, I'm then checking other sources of
info for when the notification was posted.

This is in fact why I have not upgraded past Growl 1.2.  One of my sources
of "when did that notification get posted" information is the logs viewed
via Console.app.  The extremely chatty debug info about display rect
calculation logged by Growl 1.2.1 caused me to back off to 1.2 in order to
have the necessary timing info still in the log files by the time I
checked for it.  At the time, I believe I suggested operational vs. debug
logging be done.

Optional timestamps including dates in the sticky notifications would make
secondary checks for when the event happened less necessary for me.
”””

[1]: http://groups.google.com/group/growldiscuss/msg/269dafc0942bb1e9

Original comment by p...@growl.info on 27 Apr 2011 at 6:07

[GoogleCodeExporter]

Also, we're working on a notification history viewer for a future version. Any 
users for whom the history viewer will not fulfill their need to see when 
notifications came in, please explain why not.

Original comment by p...@growl.info on 27 Apr 2011 at 6:42

[GoogleCodeExporter]

If you have a sticky alarms its common cense to me to include the time.

Original comment by Ian.Hart...@sky.com on 27 Apr 2011 at 10:43

[GoogleCodeExporter]

In my opinion the omission of a timestamp is in direct conflict with the 
intuitive nature of the Mac interface.  I can easily see when a sync has 
occurred, when an email has arrived, when an IM or Skype call started and ended 
and even when a document was created or modified.  The inability to determine 
when an event occurs that warrants a Growl alert in the first place seems to be 
almost a non-sequitur when compared to the other UI aspects of the Mac.  

A notification history viewer will be useful in tracking lengthy histories and 
trends but in the big scheme of things an average user would likely consider a 
simple timestamp on a notification the easiest means to determine roughly when 
an event occurred.  

Original comment by ScottJGoldman on 27 Apr 2011 at 12:46

[GoogleCodeExporter]

@ScottJGoldman: there are actually two aspects to the history "viewer", there 
is a full history log that is browse-able via the prefpane, but there is also a 
"notifications while you were away rollup" window that displays a list of 
notifications, with their time stamps. see attached image.

Original comment by rarich...@gmail.com on 28 Apr 2011 at 3:26

Attachments:

• rollup.png

[GoogleCodeExporter]

We'll look into this once people start using rollup so that they know how 
things are going to work going forward and if this is even necessary.

Original comment by chrisf.g...@gmail.com on 11 Aug 2011 at 6:16

• Added labels: Milestone-1.4

[GoogleCodeExporter]

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

• Added labels: Product-Growl

[GoogleCodeExporter]

Do we need this now that we have History and Rollup?

Original comment by ch...@growl.info on 14 Nov 2011 at 5:49

• Added labels: Milestone-1.5
• Removed labels: Milestone-1.4

[GoogleCodeExporter]

Original comment by ch...@growl.info on 19 Jan 2012 at 10:45

• Added labels: Milestone-2.0

[GoogleCodeExporter]

I've seen no requests for something like this since we introduced rollup. I'll 
move this to 2.1 for now.

Original comment by ch...@growl.info on 21 Jun 2012 at 4:40

• Added labels: Milestone-2.1
• Removed labels: Milestone-2.0

[GoogleCodeExporter]

Moving to the later milestone since no requests have come in after rollup came 
out.

Original comment by ch...@growl.info on 2 Oct 2012 at 8:41

• Added labels: Milestone-Later
• Removed labels: Milestone-2.1

[GoogleCodeExporter]

Rollup addresses this for me in a satisfactory way. Closing as fixed.

Original comment by ch...@growl.info on 18 Jun 2013 at 11:36

• Changed state: Fixed