Alarms aren't ordered by time

Bug #1439393 reported by Rob Taylor on 2015-04-01
This bug affects 4 people
Affects Status Importance Assigned to Milestone
ubuntu-ui-toolkit (Ubuntu)
Zsombor Egri

Bug Description

When multiple alarms are added they aren't ordered by the time the alarm is set for, which I'd have expected to be the case. See attached screenshot.

Rob Taylor (q-rob-o) wrote :
Rob Taylor (q-rob-o) wrote :

I turned a couple of alarms on and re-opened the app and the order is completely different:

Nekhelesh Ramananthan (nik90) wrote :

The clock app fetches the alarms using the Alarms API provided by the SDK and merely displays it. The ordering is done by the API. Thereby I think ubuntu-ui-toolkit is the cause of this bug.

Changed in ubuntu-clock-app:
milestone: none → 3.3
Zsombor Egri (zsombi) wrote :

Nekhelesh, you are right, the alarms are stored in a map, but the key is a pair built up using date and organiser id, so that may mess up the order.

Changed in ubuntu-ui-toolkit (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Zsombor Egri (zsombi)
Gabriele (gabrielemartelli) wrote :

This view , would solve part of the problem . It was what I proposed in this discussion :

Gabriele (gabrielemartelli) wrote :

Second image in the home clock

no longer affects: ubuntu-clock-app
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers