| 5239f09fa7309686c66d1fc70c6eacf7bdab0ab8 |
|
16-Feb-2016 |
Justin Klaassen <justinklaassen@google.com> |
Refactoring SharedPreferences to common location. - DO NOT MERGE
Bug: 25860525
Change-Id: I20a012be5aadcd743a03481a72fea7f3d4750fdd
(cherry picked from commit 942b3a3956221969c77f9abc447444505eea6929)
/packages/apps/DeskClock/src/com/android/deskclock/data/TimerDAO.java
|
| 41ad8d99d3531947b1f7016086cd0e296818b4bd |
|
16-Jan-2016 |
James Lemieux <jplemieux@google.com> |
Handle deleted timers gracefully
Bug: 26591272
Prior to dazzle, timers could inhabit a state of "DELETED" (value = 5).
In dazzle and beyond there is no reason to preserve such a state, but
it is possible for timers to exist in SharedPreferences in such a state,
so it must be handled gracefully.
Change-Id: I1754ef898dfff84c0a3e807c4bd0dd1473f87aad
/packages/apps/DeskClock/src/com/android/deskclock/data/TimerDAO.java
|
| 6d603b7c62bb38d763a681a8bf20fadb1442e833 |
|
07-Nov-2015 |
James Lemieux <jplemieux@google.com> |
Refactor Timers to use new unified DataModel
Bug: 24816218
Bug: 25494722
This refactoring introduces a Timer domain object. Instances of these
domain objects are fetched via a DataModel class that is the single point
of reference for all timer data. This allows the data to be shared across
the entire application. In particular, the timer notifications, TimerFragment
and ExpiredTimersActivity all draw upon the same model to determine
what the state of the timers are.
IMPORTANT: The public intent com.android.deskclock.action.STOP_TIMER
has been renamed to com.android.deskclock.action.PAUSE_TIMER to be
more accurate.
Change-Id: Ib904e80a25c6de1861de2b395bec27db16ff0e66
/packages/apps/DeskClock/src/com/android/deskclock/data/TimerDAO.java
|