Bug 306178 - When a collection is enabled, its alarms are added to the alarm list in the wrong order
Summary: When a collection is enabled, its alarms are added to the alarm list in the w...
Status: CLOSED FIXED
Alias: None
Product: kalarm
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: David Jarvie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-02 22:56 UTC by David Jarvie
Modified: 2020-08-17 23:43 UTC (History)
0 users

See Also:
Latest Commit: 0bb480dcd08d465d8a79ddf264a7dcbb53cca26f
Version Fixed In: KDE 4.9.4

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description David Jarvie 2012-09-02 22:56:21 UTC 
When a collection with several alarms is enabled, its alarms are not necessarily sorted according to the selected sort column's order when they are first shown. For example, if alarms are ordered by next trigger time in ascending order, the new alarms might not be.

Reproducible: Sometimes

Steps to Reproduce:
1. Enable a collection. Verify whether its alarms are ordered correctly.
2. If they are ordered correctly:
  a) Reverse the sort order by clicking in the sort column's header.
  b) Disable and re-enable the collection. This time the order should be wrong.
Comment 1 David Jarvie 2012-11-14 01:20:36 UTC 
Fixed for KDE 4.9.4.
Git commits 0bb480dcd08d465d8a79ddf264a7dcbb53cca26f (4.9 branch), 0438f62e95660de4fe01d817e9651f31c798c417 (master)