Open cpeppas opened 5 years ago
I ran into this as well. Business requirement is to have a registration flow with sliding animation, and the second screen is date of birth. It has to have a customized header with flow progress indicator, so a dialog won't do, neither as full screen nor modal. The current screen uses a Windows Phone style picker from years ago, so I wanted to replace it. What's infuriating me is, that as the name suggests, a fragment should be used as a part of a screen, instead it's used as a full screen or as a dialog nowadays. Things are shifted. It seems to me this will never be solved as pickers are dialogs, so we need another custom solution. Blimey!
A DialogFragment is designed to be used as a Dialog or a Fragment. It's ridiculous that you can't just insert the fullscreen version or the dialog in to a view as a fragment. Makes zero sense.
This feature request should not be ignored by Google, since it contradicts their own documentation found here: https://developer.android.com/develop/ui/views/components/pickers
That page says:
We recommend you use DialogFragment to host each time or date picker. The DialogFragment manages the dialog lifecycle for you and lets you display pickers in different layout configurations, such as in a basic dialog on handsets or as an embedded part of the layout on large screens.
Description: My aim is to create a MaterialDatePicker dialogfragment but instead of displaying as a dialog to use it as a normal embedded fragment
Expected behavior: The datepicker to work normally as embedded fragment
Actual behavior: App crashes with the following tracktrace
Source code: Using the catalog demo app from this repository
Android API version: minSkd 21 - targetSdk 28
Material Library version: Material Android Library version 1.1.0-beta01
Device: Emulator Nexus6 API:24 x86