showPersianDateRangePicker function

Future<JalaliRange?> showPersianDateRangePicker({ required BuildContext context, JalaliRange? initialDateRange, required Jalali firstDate, required Jalali lastDate, Jalali? currentDate, PersianDatePickerEntryMode initialEntryMode = PersianDatePickerEntryMode.calendar, String? helpText, String? cancelText, String? confirmText, String? saveText, String? errorFormatText, String? errorInvalidText, String? errorInvalidRangeText, String? fieldStartHintText, String? fieldEndHintText, String? fieldStartLabelText, String? fieldEndLabelText, Locale? locale, bool barrierDismissible = true, Color? barrierColor, String? barrierLabel, bool useRootNavigator = true, RouteSettings? routeSettings, TextDirection? textDirection, TransitionBuilder? builder, Offset? anchorPoint, TextInputType keyboardType = TextInputType.datetime, Icon? switchToInputEntryModeIcon, Icon? switchToCalendarEntryModeIcon, required Jalali initialDate, })

Shows a full screen modal dialog containing a Material Design date range picker.

The returned Future resolves to the JalaliRange selected by the user when the user saves their selection. If the user cancels the dialog, null is returned.

If initialDateRange is non-null, then it will be used as the initially selected date range. If it is provided, initialDateRange.start must be before or on initialDateRange.end.

The firstDate is the earliest allowable date. The lastDate is the latest allowable date.

If an initial date range is provided, initialDateRange.start and initialDateRange.end must both fall between or on firstDate and lastDate. For all of these Jalali values, only their dates are considered. Their time fields are ignored.

The currentDate represents the current day (i.e. today). This date will be highlighted in the day grid. If null, the date of Jalali.now() will be used.

An optional initialEntryMode argument can be used to display the date picker in the PersianDatePickerEntryMode.calendar (a scrollable calendar month grid) or PersianDatePickerEntryMode.input (two text input fields) mode. It defaults to PersianDatePickerEntryMode.calendar.

An optional switchToInputEntryModeIcon argument can be used to display a custom Icon in the corner of the dialog when DatePickerEntryMode is DatePickerEntryMode.calendar. Clicking on icon changes the DatePickerEntryMode to DatePickerEntryMode.input. If null, Icon(useMaterial3 ? Icons.edit_outlined : Icons.edit) is used.

An optional switchToCalendarEntryModeIcon argument can be used to display a custom Icon in the corner of the dialog when DatePickerEntryMode is DatePickerEntryMode.input. Clicking on icon changes the DatePickerEntryMode to DatePickerEntryMode.calendar. If null, Icon(Icons.calendar_today) is used.

The following optional string parameters allow you to override the default text used for various parts of the dialog:

• helpText, the label displayed at the top of the dialog.
• cancelText, the label on the cancel button for the text input mode.
• confirmText,the label on the ok button for the text input mode.
• saveText, the label on the save button for the fullscreen calendar mode.
• errorFormatText, the message used when an input text isn't in a proper date format.
• errorInvalidText, the message used when an input text isn't a selectable date.
• errorInvalidRangeText, the message used when the date range is invalid (e.g. start date is after end date).
• fieldStartHintText, the text used to prompt the user when no text has been entered in the start field.
• fieldEndHintText, the text used to prompt the user when no text has been entered in the end field.
• fieldStartLabelText, the label for the start date text input field.
• fieldEndLabelText, the label for the end date text input field.

An optional locale argument can be used to set the locale for the date picker. It defaults to the ambient locale provided by Localizations.

An optional textDirection argument can be used to set the text direction (TextDirection.ltr or TextDirection.rtl) for the date picker. It defaults to the ambient text direction provided by Directionality. If both locale and textDirection are non-null, textDirection overrides the direction chosen for the locale.

The context, barrierDismissible, barrierColor, barrierLabel, useRootNavigator and routeSettings arguments are passed to showDialog, the documentation for which discusses how it is used.

The builder parameter can be used to wrap the dialog widget to add inherited widgets like Theme.

A DisplayFeature can split the screen into sub-screens. The closest one to anchorPoint is used to render the content.

If no anchorPoint is provided, then Directionality is used:

• for TextDirection.ltr, anchorPoint is Offset.zero, which will cause the content to appear in the top-left sub-screen.
• for TextDirection.rtl, anchorPoint is Offset(double.maxFinite, 0), which will cause the content to appear in the top-right sub-screen.

If no anchorPoint is provided, and there is no Directionality ancestor widget in the tree, then the widget asserts during build in debug mode.

State Restoration

Using this method will not enable state restoration for the date range picker. In order to enable state restoration for a date range picker, use Navigator.restorablePush or Navigator.restorablePushNamed with PersianDateRangePickerDialog.

For more information about state restoration, see RestorationManager.

To test state restoration on Android:

1. Turn on "Don't keep activities", which destroys the Android activity as soon as the user leaves it. This option should become available when Developer Options are turned on for the device.
2. Run the code sample on an Android device.
3. Create some in-memory state in the app on the phone, e.g. by navigating to a different screen.
4. Background the Flutter app, then return to it. It will restart and restore its state.

To test state restoration on iOS:

1. Open ios/Runner.xcworkspace/ in Xcode.
2. (iOS 14+ only): Switch to build in profile or release mode, as launching an app from the home screen is not supported in debug mode.
3. Press the Play button in Xcode to build and run the app.
4. Create some in-memory state in the app on the phone, e.g. by navigating to a different screen.
5. Background the app on the phone, e.g. by going back to the home screen.
6. Press the Stop button in Xcode to terminate the app while running in the background.
7. Open the app again on the phone (not via Xcode). It will restart and restore its state.

{@tool dartpad} This sample demonstrates how to create a restorable Material date range picker. This is accomplished by enabling state restoration by specifying MaterialApp.restorationScopeId and using Navigator.restorablePush to push PersianDateRangePickerDialog when the button is tapped.

** See code in examples/api/lib/material/date_picker/show_date_range_picker.0.dart ** {@end-tool}

See also:

• showPersianDatePicker, which shows a Material Design date picker used to select a single date.
• JalaliRange, which is used to describe a date range.
• DisplayFeatureSubScreen, which documents the specifics of how DisplayFeatures can split the screen into sub-screens.

Implementation

Future<JalaliRange?> showPersianDateRangePicker({
  required BuildContext context,
  JalaliRange? initialDateRange,
  required Jalali firstDate,
  required Jalali lastDate,
  Jalali? currentDate,
  PersianDatePickerEntryMode initialEntryMode =
      PersianDatePickerEntryMode.calendar,
  String? helpText,
  String? cancelText,
  String? confirmText,
  String? saveText,
  String? errorFormatText,
  String? errorInvalidText,
  String? errorInvalidRangeText,
  String? fieldStartHintText,
  String? fieldEndHintText,
  String? fieldStartLabelText,
  String? fieldEndLabelText,
  Locale? locale,
  bool barrierDismissible = true,
  Color? barrierColor,
  String? barrierLabel,
  bool useRootNavigator = true,
  RouteSettings? routeSettings,
  TextDirection? textDirection,
  TransitionBuilder? builder,
  Offset? anchorPoint,
  TextInputType keyboardType = TextInputType.datetime,
  final Icon? switchToInputEntryModeIcon,
  final Icon? switchToCalendarEntryModeIcon,
  required Jalali initialDate,
}) async {
  assert(
    initialDateRange == null ||
        !initialDateRange.start.isAfter(initialDateRange.end),
    "initialDateRange's start date must not be after it's end date.",
  );
  initialDateRange = initialDateRange == null
      ? null
      : PersianDateUtils.datesOnly(initialDateRange);
  firstDate = PersianDateUtils.dateOnly(firstDate);
  lastDate = PersianDateUtils.dateOnly(lastDate);
  assert(
    !lastDate.isBefore(firstDate),
    'lastDate $lastDate must be on or after firstDate $firstDate.',
  );
  assert(
    initialDateRange == null || !initialDateRange.start.isBefore(firstDate),
    "initialDateRange's start date must be on or after firstDate $firstDate.",
  );
  assert(
    initialDateRange == null || !initialDateRange.end.isBefore(firstDate),
    "initialDateRange's end date must be on or after firstDate $firstDate.",
  );
  assert(
    initialDateRange == null || !initialDateRange.start.isAfter(lastDate),
    "initialDateRange's start date must be on or before lastDate $lastDate.",
  );
  assert(
    initialDateRange == null || !initialDateRange.end.isAfter(lastDate),
    "initialDateRange's end date must be on or before lastDate $lastDate.",
  );
  currentDate = PersianDateUtils.dateOnly(currentDate ?? Jalali.now());
  assert(debugCheckHasMaterialLocalizations(context));

  Widget dialog = PersianDateRangePickerDialog(
    initialDateRange: initialDateRange,
    firstDate: firstDate,
    lastDate: lastDate,
    currentDate: currentDate,
    initialEntryMode: initialEntryMode,
    helpText: helpText,
    cancelText: cancelText,
    confirmText: confirmText,
    saveText: saveText,
    errorFormatText: errorFormatText,
    errorInvalidText: errorInvalidText,
    errorInvalidRangeText: errorInvalidRangeText,
    fieldStartHintText: fieldStartHintText,
    fieldEndHintText: fieldEndHintText,
    fieldStartLabelText: fieldStartLabelText,
    fieldEndLabelText: fieldEndLabelText,
    keyboardType: keyboardType,
    switchToInputEntryModeIcon: switchToInputEntryModeIcon,
    switchToCalendarEntryModeIcon: switchToCalendarEntryModeIcon,
  );

  if (textDirection != null) {
    dialog = Directionality(
      textDirection: textDirection,
      child: dialog,
    );
  }

  if (locale != null) {
    dialog = Localizations.override(
      context: context,
      locale: locale,
      child: dialog,
    );
  }

  return showDialog<JalaliRange>(
    context: context,
    barrierDismissible: barrierDismissible,
    barrierColor: barrierColor,
    barrierLabel: barrierLabel,
    useRootNavigator: useRootNavigator,
    routeSettings: routeSettings,
    useSafeArea: false,
    builder: (BuildContext context) {
      return builder == null ? dialog : builder(context, dialog);
    },
    anchorPoint: anchorPoint,
  );
}