when creating an alarm, app can reach a state where hour can't be set
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Clock App |
Invalid
|
High
|
Nekhelesh Ramananthan |
Bug Description
See linked video.
This is consistently repeatable for me with these prerequisites: (1) I try to set the alarm immediately after the clock app is launched, and (2) I try to tap on the desired alarm hour instead of dragging the hour hand to it. Once those two prerequisites are done, I get the behavior in the video:
1. Dragging the hour hand updates the new alarm's minute property, leaving the hour unchanged. Even though the minute property tracks the user's finger movement, the hour hand itself doesn't move.
2. If you try a second time to drag the hour hand, it still won't move, nor will any of the alarm's properties change.
3. Clicking on the time in the middle of the clock seems to reset the state s.t. you can then drag the hour hand and set the hour properly.
4. Clicking on the time in the middle of the clock a second time correctly switches to the setting-
Related branches
- PS Jenkins bot: Approve (continuous-integration)
- Alan Pope 🍺🐧🐱 🦄 (community): Approve
- Ubuntu Phone Apps Jenkins Bot: Approve (continuous-integration)
-
Diff: 27 lines (+3/-0)1 file modifiedcommon/ClockBase.qml (+3/-0)
Changed in ubuntu-clock-app: | |
milestone: | none → 2.2 |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in ubuntu-clock-app: | |
milestone: | 2.2 → alarm-blockers |
Changed in ubuntu-clock-app: | |
status: | Confirmed → In Progress |
assignee: | nobody → Nekhelesh Ramananthan (nik90) |
Changed in ubuntu-clock-app: | |
status: | Confirmed → Invalid |
Fix committed into lp:ubuntu-clock-app at revision 413, scheduled for release in ubuntu-clock-app, milestone 2.2