| Age | Commit message (Collapse) | Author |
|---|
|
* Since Android 12 introduced a new style, try to mimic it for this app
* Due to AndroidX and the support libraries still being old, we have to,
like Settings does with SettingsLib, create our own styles in the
desired looks
* Also adjust the color scheme to reflect Material You
* We deviated from AOSP already quite a bit, so we don't need to really
care about the change's footprint
* Clean up behind us by removing (now unused) resources and includes in
files that were modified anyways (and adjust order while on it)
* Copy CollapsibleToolbarBaseActivity and required resources from
SettingsLib - that way we can mimic the style easily without having
to move this app to system_ext or using privileged_api
* Since we always use dark layout, modify slightly so it works for us
* Remove things we don't need so we don't have to copy too many files
from SettingsLib
Change-Id: I4c81e03c71f468a9e468426a8233ad96059cb05d
|
|
Test: compile and open
Bug: 76692459
Change-Id: Ibf8e95a917fbe3e364340ed1c5fba6e66f2d8afd
|
|
Bug: 34863910
Test: Manually create a new timer and observe the fab
Change-Id: Ib0a1e3ffa84f459c590a3ef82a18b848404741f5
|
|
- Cleanup layouts and styles.
- Ensure proper theming support.
Bug: 25693255
Bug: 33416420
Test: manually verified timer setup screen in different configurations
Change-Id: Ib0715633c003d4ad672bc413dfd0be5e269b3b09
|
|
Bug: 25693255
Test: manual - basic sanity check on API 25 device
Change-Id: I2a7e9ccfc695017a91b66a88e71b769f8da667ef
|
|
Bug: 32703589
These animations used to occur serially. To parallelize them,
new UpdateTypes were added to only shrink and only expand
the fab and buttons. This allows these animations to be
synchronized with other animations that alter the view.
Also, creating the new timer had to be delayed until after
hiding the fab and buttons so that their state was consistent
as they shrunk. This mirrors the delayed removal of timers
that already existed.
Change-Id: I381b86fd55d5d51c522138c2b51996594da7f85e
|
|
Bug: 30810789
Test: Manually verified play/pause icon animates in timer/stopwatch.
Change-Id: Ib81fba107c7299b4aaf7f9313ee68429b31e82ff
|
|
|
|
Bug: 29939321
When reading back the time being set, Talkback will
now sound like a veritable human being.
Change-Id: I5eb17d305a80295d5a3051ee25b252ae912baaf1
|
|
Bug: 29804269
When using talkback and using the delete button on the
create new timer screen, talkback will now say "delete #
button" with the correct #.
Change-Id: I11782a98981f21cb70a0745a92b5e7f2a8be96bc
|
|
Bug: 25793040
Change-Id: I2c33e23d2cd1d521c4deb13b0aaed381522ef189
|
|
Bug: 26055290
External keyboard number keys and backspace
can now be used to create a timer.
Change-Id: Idff9fac44d25f3e9e4cd6e84d64bce778e15ab7d
|
|
Bug: 26840878
Change-Id: I641090f90f2063964992a714b7f22f5ed3e19f92
|
|
Bug: 28065873
String.format(...) was being called in a tight loop to format various
times (e.g. lap times, accumulated times, etc) when laps exist. This produces
more garbage for the VM to collect than is necessary. Formatting the
times directly into a reusable StringBuilder significantly reduces the
memory churn and removes intermittent GC pauses on older platforms
and low-memory devices.
Change-Id: Iad574cea7f827623bb4854458d43df76967d8c62
|
|
Bug: 28026276
Change-Id: I9d2f12d96bf1d32e66a6f6023f6bfb5d90b3eccc
|
|
Bug: 26292420
Change-Id: Ib5d8b09fa9d70f408c3097654bae5b6906fac048
|
|
TimerSetupView used to have its own fab and a custom button for
the X icon that cancels timer creation. It now utilizes the application's
fab and buttons. This ensures that fab/button locations and
animations are uniform.
Child fragments and views no longer have direct access to the fab
and buttons outside of specific callbacks. This design attempts
to remove past bugs where irrelevant views altered the state of the
fab at inappropriate times.
Change-Id: If8c69246e915f6357df80a6d8107f7b2b5a6172e
|
|
Bug: 25843144
Attempting to view a specific timer trumps the timer setup screen
in all cases. onResume() now enforces that policy. The timer setup
screen is still displayed in all other cases, including:
- no timers exist
- the intent indicates a new timer should be created
- the last visible timer screen was the timer setup screen
Change-Id: I28d147cadeb29055fa0c68a44da6648f6ad33238
|
|
Bug: 25779786
The issue here is that TimerSetupView actually customizes the fab.
These customizations include setting it invisible. It was a poor design
to share the fab with this view. So, the fix is that the view now holds
its own fab-like button that it is free to manipulate without fear of
altering the app-wide fab state unintentionally.
Change-Id: Ie83b03c98db4f77e0be912b122b6f74c2c7e6c8a
|
|
Change-Id: Ibe429ba988a8842715c8732b4524eefb2655f7e4
|
|
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
|
|
Change-Id: I805316cc11f6a8b3e4dd40f1368f386df536d612
|
|
Change-Id: I0aa60c2fdb47d59378cd485f4508515d8830104d
|
