Open GoogleCodeExporter opened 9 years ago
This won't get fixed in 2.0, as 2.0 is already in the hands of Apple for
review. Setting this on the 2.1 milestone, although if we have to do a 2.0.1
for a more serious issue, it might wind up resolved in it.
Original comment by dan...@growl.info
on 10 Sep 2012 at 2:06
Bumping to 2.2
Original comment by dan...@growl.info
on 28 Apr 2013 at 8:49
Issue 597 has been merged into this issue.
Original comment by ch...@growl.info
on 23 Jun 2013 at 6:13
Arg... I knew this had to have been reported and could not find it again with
some searches... Sorry.
The merge is perfect.
Original comment by yann.ric...@gmail.com
on 23 Jun 2013 at 6:53
I don't know if that issue opened one year ago has to wait to Milestone-2.2.
But, out of experience, its visibility is much larger and worse than the
scenario described in the first message posted.
The fact is that, when the user goes to the history pane where he thinks he'll
find its recent notifications sorted by time, it's quite NEVER sorted by time
(even if the Time column is still highlighted) and not even sorted at all to be
true.
Why, and how to reproduce the bug:
- go the the History pane and click on "Time" to have notifications sorted by
date.
- leave the preference pane.
- as soon as a new notification will be produced with Growl, then going back
to the History preference pane display a totally jumbled display:
1) the last column selected as order criterion is still highlighted (here
"Time")
2) but all the entries (the one before the last visit and the new ones) are
totally jumbled: no sense in that sort (not sorted by Application, nor by
Message, nor by Time...) Arg ???
Then currently, the only solution to see a sorted display of recent
notifications in the history tab is to manually re-sort the list each time you
go to the History tab.
(the only case where you can avoid this manual re-sort is when... there were no
new notifications at all after your last visit ;-))
Original comment by yann.ric...@gmail.com
on 30 Oct 2013 at 6:14
Original issue reported on code.google.com by
I.atent.dead@gmail.com
on 8 Sep 2012 at 11:04