Access to the close button to allow subclasses to manipulate positioning and appearance.

Top Content View to add subviews for top labels. Think of it as a header view. Will take into account adjusting the content view top anchor point based on if the topContentView is used or not. A topContentView will be enabled once accessed via the property.

Content View to add subviews A lot like UITableViewCell.contentView this will be used to determine proper sizing of the view. However since we are inherintely different (and more configurations are possible such as adding a UIScrollView as a subview) there are some notable differences. If no minimumHeight is defined and we’re not of a fixed size: - The maximum amount we will show before isExapandable will be YES is 1/3 of the total screen size. If subviews are added that will cause our height to be beyond that OR if a UIScrollView (or subclass such as UITableView/UICollectionView) is added as a subview we will allow expanding to the maximum sheet size regardless of contents - Minimum height will be automatically calulcated to fit the content or 1/3 of the screen. Whichever is less (padding is automatically added) - If one of the previous configurations causes us to automatically set isExpandable to YES, toggling it to NO will have no effect. To properly set a bottom constraint, set your external constraint priority to UILayoutPriorityDefaultHigh, at least, to avoid conflicts with this class’s internal contentView bottom constraint.

When a bottom sheet is presented in the MRMapViewController by default it will appear above the UITabBar (if one exists of course). If this property is set to NO (and the UITabBarController it resides in implements the MRDHidableTabBar protocol) the tabbar will be hidden before the sheet is displayed.

Current sheet state. Useful for reacting to changes in our size on screen.

The lowest height that a sheet should appear.

Used for specifying the maximum height a floating sheet can become as a percentage of the screen. This only applies expandable floating sheets, which are usually found on devices with regular horizontal size classes.

The fixed height the sheet will be presented at. Only set/applicable if - (instancetype)initWithCloseEnabled:(BOOL)closeEnabled fixedHeight:(CGFloat)fixedHeight was used for instantiation.

BOOL to check if we are a fixed size

Boolean to determine if we should be able to drag the the sheet up.

Determine whether the bottom sheet can float when on a large enough screen (such as a tablet). Defaults to YES, subclasses can return NO to opt out.

Whether the close button is enabled with this type of sheet.

Boolean for if this sheet should not dismiss without either being explicitly closed or forced to dismiss. Useful for things like direction where we want the sheet to remain visible even if the user taps on the map in arbitrary locations.

A mechanism to display when a sheet may be loading content or not. YES will display a white translucent overlay with an activity indicator. NO will remove the overlay and animating. Changes to this property will trigger -contentUpdated to be called

Actions for when a sheet has internal actions and outsiders need to know about them.

Determines the intial state of the bottom sheet as MRDBottomSheetStateHidden or MRDBottomSheetStateMinimum. Defaults to YES.

Determines the state of the bottom sheet immediately after it appears. Defaults to MRDBottomSheetStateMaximum.

Determines the state of the bottom sheet after the keyboard disappears. Defaults to MRDBottomSheetStateMinimum.

Use this constant to tweak bottom padding after super sets it in contentUpdated. Defaults to 46 points.

Use this to determine the initial state of the BottomSheet containing the instance of this AbstractController subclass when it first appears.

This is added to the height calculated for MRDBottomSheetStateMinimum to determine the containing BottomSheet height for MRDBottomSheetStatePeek.

Our content has been updated so we should reflow our layout to make sure everything appears as it should. When isLoading is changed, this method is called

The best way to create a subclass sheet view controller. Make sure to override this method if you would like to add default behavior such as minimum height changes.

The best way to create a subclass sheet view controller. Make sure to override this method if you would like to add default behavior such as minimum height changes.

The best way to create a subclass sheet view controller if you want it to only ever appear at once size and not be expandable.

The best way to create a subclass sheet view controller. Make sure to override this method if you would like to add default behavior such as minimum height changes.

The best way to create a subclass sheet view controller. Make sure to override this method if you would like to add default behavior such as minimum height changes.

The best way to close and dismiss the sheet.

Provides the ability to pass a drag / pan gesture to the parent view controller to drag a sheet up and down. This can come into play when there are other elements such as table views and scroll views that may capture gesutre recognition but should cause the sheet to move regardless.