When calling both setFabAlignmentMode and replaceMenu, the fab alignment animation and menu animation were not properly coordinating. replaceMenu causes a call to onLayout, which immediately updates the menu's translationX, causeing the menu to jump to its final position. This adds a condition to skip the menu position update if a menu animatior is running.
Additionally, the menu's contents were immediately being swapped making the animation look jumpy. This CL also as a method to update the fab alignment and menu resource at the same time so a coordinated animation of: fab scale out/slide start - > menu fade out -> menu replaced -> menu fade in -> fab scale/slide finish, can be run.
PiperOrigin-RevId: 316860005
- Added attribute cornerRadius.
- Added rounded corner support for linear determinate and indeterminate (non-seamless) mode.
- Added rounded corner support for circular determinate and indeterminate mode.
- Added screenshot tests.
- Modified show cases in Catalog to demo this feature.
PiperOrigin-RevId: 316400672
* Removed update color control.
* a11y improvements:
* Added announcements for when customizable fields are updated.
* Removed individual update buttons. Update is now done through imeActions for each text field (via the done button on the keyboard).
PiperOrigin-RevId: 316168847
Slider throws an exception when calling getValue with more than one value. Supporting both single value and multiple values in the same class makes it confusing. While not supporting convenience methods getValue and setValue in the multi value class makes it, well, inconvenient.
In addition min, max are also a bit ambiguous since seekBar uses these for valueFrom and valueTo so those were removed.
PiperOrigin-RevId: 311774410
Switch the container transform to use a transition listener instead of an animator listener. A transition listener calls onTransitionStart as soon as the transition begins where an animator listener calls onAnimatorStart after the transitions delay, if any, casuing an unwanted visual flash of the end view before the animator starts.
PiperOrigin-RevId: 309977033
This updaes the remaining transitions to compose themselves of two animators instead of two visibility transitions. This also removes the context parameter from MaterialFadeThrough, MaterialFade and MaterialSharedAxis' constructors.
PiperOrigin-RevId: 303332658
The alternative to android:editable="false" (which is deprecated) is to set inputType="none", however due to a framework bug that has no effect. This change makes it so it works as expected.
PiperOrigin-RevId: 299411110
The new recommendation is to use com.google.android.material.MaterialContainerTransform instead of the transformation library.
Also delete the catalog demo for transformation.
PiperOrigin-RevId: 297171082
And rename it from ic_transformation to ic_transitions.
Currently the shape catalog demo's icon is used for transitions, but there's an icon that was created for transformations that would be more fitting for the transitions catalog demo.
PiperOrigin-RevId: 296210450
Add a container transform demo similar to the activity and fragment container transform demos, but for view to view transitions.
PiperOrigin-RevId: 296048253
