Summaryīy using :material we only need to write a few XML codes to achieve the fancy transformation animations for the floating action button. The custom behavior inherited the ExpandableTransformationBehavior and here is the source code. Here is a custom behavior example that let the speed dial actions views appear sequentially:
#MATERIAL DESIGN ANIMATION ANDROID FULL#
Then just bind the full class name to views via app:layout_behavior. To create our own animation when tExpanded(boolean) was called, we need to create custom behavior class that inherit one of these transformation behaviors: If you are interested in the implementation detail, the related source code can be found here: The working flow is very similar to the speed dial but a little more complicated. To transform the FAB into the target view we can call tExpanded(true) or transform the FAB back by calling tExpanded(false).
#MATERIAL DESIGN ANIMATION ANDROID ANDROID#
Android 5.0 (API level 21) and above lets you customize these. When FloatingActionButton.isExpanded() = false only the FAB will show and vice verse. Animations in material design give users feedback on their actions and provide visual continuity as users interact with your app. If the target view is not a CircularRevealWidget then no morph animation will appear. The material design components library already provided some often used layouts that implemented CircularRevealWidget for us, like CircularRevealFrameLayout. Notice that there is another requirement for the target view that the view must be a CircularRevealWidget. Set the stroke color using the strokeColor attribute.
Stroke width can be set using the strokeWidth attribute. The widget will display the correct default Material styles without the use of a style flag. Similar to the speed dial implementation, a specific behavior class .transformation.FabTransformationSheetBehavior need to be bind to the target view. This class supplies Material styles for the card in the constructor. Morphing should be reversible and transform the new surface back into the FAB.Ĭreate a CoordinatorLayout that contains two child views, a FAB and a target view that the FAB will transform into. The Material motion system, recently released as part of the MDC-Android library (v 1.2.0), distills common transitions into a group of simple patterns for a smoother, more understandable user experience. The FAB can transform into another surface in an app.
When the expanded state of ExpandableWidget changes, ExpandableWidgetHelper will notify the CoordinatorLayout so the CoordinatorLayout can dispatch these changes to the FabTransformationScrimBehavior.įinally, FabTransformationScrimBehavior will respond to the state changes and create the show/hide animators for attached view. The two methods boolean isExpanded() and boolean setExpanded(boolean expanded) of the FloatingActionButton are inherited from the ExpandableWidget interface.Ī bridge class ExpandableWidgetHelper is used to connect the ExpandableWidget and the parent CoordinatorLayout.
0 kommentar(er)
