Bug: Sorting/display issue when deleting history items

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Obtain at least three or four items (with different time stamps) in your 
Growl history

2. In Growl preferences, go to the History tab

3. The history items should probably be sorted by 'Time' by default, but just 
in case, make sure to click the 'Time' header until it's sorted with the most 
recent items at the top

4. Try to delete any history item in the list by clicking the little minus 
button in the lower left

What is the expected output?
The list should remain in the exact same sort order that it was before, minus 
of course the deleted item.

What do you see instead?
Typically the entire list re-orders itself in a seemingly random fashion.

What version of the product are you using? On what operating system?
Growl 1.3.1
OS X 10.7.2
iMac 7,1

Please provide any additional information below.
As a more detailed example of what i'm describing, for instance, just now i had 
a list that looked like this:

Linkinus — New Private Message — 03:20
Linkinus — New Private Message — 03:19
Linkinus — New Highlight — 03:18
Firefox — Aurora 10.0a2 available — 03:17
Quicksilver — アイセリアの過去 — 03:05
Linkinus — New Highlight — 03:00

I highlighted the Linkinus item at 03:19 and deleted it. After doing so, my 
list suddenly appeared like this:

Linkinus — New Private Message — 03:20
Firefox — Aurora 10.0a2 available — 03:17
Quicksilver — アイセリアの過去 — 03:05
Linkinus — New Highlight — 03:18
Linkinus — New Highlight — 03:00

Note that the 03:18 highlight now appears in between 03:00 and 03:05 — this 
despite the fact that the list header still shows it is being sorted by 
descending time.

If i switch away from the History tab and return to it, the list stays sorted 
in this manner. However, if a new notification gets added to the history as i'm 
looking at it, the list will re-order itself back to the way it's supposed to 
be. (03:18 will go back up between 03:17 and 03:20)

I can create a screen recording of this behaviour if you like, but hopefully 
that's enough to go on. Somewhat trivial, but still annoying :)

Original issue reported on code.google.com by dana.my....@gmail.com on 27 Nov 2011 at 9:39

[GoogleCodeExporter]

Fixed for 1.4, apologies for the length of delay in responding, just got around 
to catching up on tickets that never got sorted properly.  (also, hooray for 
fixes that take one line of code),

Original comment by dan...@growl.info on 1 Feb 2012 at 4:26

• Changed state: FixedInSource
• Added labels: Milestone-1.4, Product-Growl

[GoogleCodeExporter]

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

• Changed state: Fixed