[API Request] Alarms API should expose a slot Update() to allow app devs to manually refresh the model

Bug #1380559 reported by Nekhelesh Ramananthan
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntu-ui-toolkit (Ubuntu)
Fix Released
High
Zsombor Egri
Vivid
New
Undecided
Unassigned
ubuntu-ui-toolkit (Ubuntu RTM)
New
Undecided
Unassigned

Bug Description

Use Case: When a repeating alarm is triggered, the alarm date still shows the old date instead of the next new alarm date. There is nothing the Ubuntu SDK can do since it doesn't get the signal when an alarm is triggered. But the clock app can check that and update the alarm model accordingly which in turn would update the alarm date.

Tags: rtm14

Related branches

Zsombor Egri (zsombi)
Changed in ubuntu-ui-toolkit:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Zsombor Egri (zsombi)
importance: High → Critical
tags: added: rtm14
Revision history for this message
Victor Tuson Palau (vtuson) wrote :

I think this is high rather than critical

Revision history for this message
Zsombor Egri (zsombi) wrote :

@Victor, a comment from Nekhelesh in IRC:
13:26 zsombi: does it affect any rtm functionality 4 u?
13:27 nik90: zsombi: yes since when a repeating alarm is triggered, the clock app bottom edge reads "No Active Alarms" since the alarm date has passed.

So if you consider this not being important for RTM, we can lower its priority.

Zsombor Egri (zsombi)
Changed in ubuntu-ui-toolkit:
importance: Critical → High
Revision history for this message
Nekhelesh Ramananthan (nik90) wrote :

Steps to reproduce bug in clock app:
1. Open clock app and create a *repeating* alarm to ring in the next few minutes and repeats Today and Tomorrow. (Please make sure this newly created repeating alarm is the only alarm saved in the clock app)
2. Go back to the main clock page
3. Wait for the alarm to ring and then dismiss it.
4. Notice that the bottom edge now reads "No Active Alarms" instead of showing the remaining time to the alarm to ring tomorrow.

This leads to a bad user experience and can potentially confuse the user about whether the alarm will actually go of tomorrow or not. Please raise this as critical and needs to be fixed for RTM.

Revision history for this message
Joe Odukoya (jodukoya) wrote :

I have to say that this has to be considered High.

I agree that this is not a good user experience (i.e. it is bad) but the alarms feature itself does actually work.

We definitely need to fix this but it cannot be considered critical at this stage.

Zoltan Balogh (bzoltan)
Changed in ubuntu-ui-toolkit:
milestone: none → 11.07
Zsombor Egri (zsombi)
Changed in ubuntu-ui-toolkit:
status: Triaged → In Progress
Zoltan Balogh (bzoltan)
Changed in ubuntu-ui-toolkit (Ubuntu):
assignee: nobody → Zsombor Egri (zsombi)
importance: Undecided → High
status: New → In Progress
Zoltan Balogh (bzoltan)
no longer affects: ubuntu-ui-toolkit
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntu-ui-toolkit - 1.1.1347+15.04.20141126-0ubuntu1

---------------
ubuntu-ui-toolkit (1.1.1347+15.04.20141126-0ubuntu1) vivid; urgency=medium

  [ Zsombor Egri ]
  * Expose refresh() function in revision 1 (Ubuntu.Components 1.1).
    Fixes LP: #1380559
  * Alarm adaptation refactored to support change granular model
    updates. Fixes LP: #1322558, LP: #1360359, LP: #1370649,
    LP: #1380553
  * Fix Header thin divider margins, restored to original no-margins.
    Fixes LP: #1380766.

  [ Tim Peeters ]
  * Add ensure_visible() function to header AP helper.
    Fixes LP: #1363591

  [ Albert Astals Cid ]
  * Add context support for i18n.tr calls. This allows to have strings
    like "All" translated to two different strings in the translated
    language if different contexts are given. Fixes LP: #1394904
 -- Ubuntu daily release <email address hidden> Wed, 26 Nov 2014 08:33:25 +0000

Changed in ubuntu-ui-toolkit (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.