Scaffold.floatingActionButton is scaled down through an animation with a Curves.easeIn, andĭisappears when the bottom sheet covers the entire Scaffold.Īnd as soon as the bottom sheet is dragged down to cover less than 70% of the Scaffold, the scrimĭisappears and Scaffold.floatingActionButton animates back to its normal size.Scaffold starts to show scrim (see ScaffoldState.showBodyScrim), and.Scaffold.floatingActionButton is set, and the bottom sheet is dragged toĬover greater than 70% of the Scaffold's height, two things happen in parallel: If Scaffold.bottomSheet is a DraggableScrollableSheet, Floating action button with a draggable scrollable bottom sheet Widget can be used within the scaffold's body to avoid areas The scaffold's body is not inset by this padding valueĪlthough an appBar or bottomNavigationBar will typicallyĬause the body to avoid the padding. Not be completely visible, like the display "notch" on the iPhone The MediaQueryData.padding value defines areas that might Widget will be scrolled into view if it's within a scrollable By default the scaffold's body is resized to make Widget's MediaQueryData.viewInsets changes and the Scaffold willīe rebuilt. The device's keyboard appears the Scaffold's ancestor MediaQuery Means that it will occupy its entire window or device screen. The scaffold will expand to fill the available space. To create a local project with this code sample, run:įlutter create -sample=material.Scaffold.3 mysample Scaffold layout, the keyboard, and display "notches"
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |