void zApplyAllowEmptyDates(){
  if (!hasParent()) {
    return;
  }
  LocalDate selectedDate=zGetParentSelectedDate();
  if ((!allowEmptyDates) && (selectedDate == null)) {
    LocalDate today=LocalDate.now();
    if (InternalUtilities.isDateVetoed(vetoPolicy,today)) {
      throw new RuntimeException("Exception in DatePickerSettings.zApplyAllowEmptyDates(), " + "Could not initialize a null date to today, because today is vetoed by " + "the veto policy. To prevent this exception, always call "+ "setAllowEmptyDates() -before- setting a veto policy.");
    }
    zSetParentSelectedDate(today);
  }
}

void zApplyAllowEmptyDates ( ) { if ( ! hasParent ( ) ) { return ; } LocalDate selectedDate = zGetParentSelectedDate ( ) ; if ( ( ! allowEmptyDates ) && ( selectedDate == null ) ) { LocalDate today = LocalDate . now ( ) ; if ( InternalUtilities . isDateVetoed ( vetoPolicy , today ) ) { throw new RuntimeException ( "Exception in DatePickerSettings.zApplyAllowEmptyDates(), " + "Could not initialize a null date to today, because today is vetoed by " + "the veto policy. To prevent this exception, always call " + "setAllowEmptyDates() -before- setting a veto policy." ) ; } zSetParentSelectedDate ( today ) ; } }
zapplyallowemptydates , this applies the named setting to the parent component . implementation notes : this cannot throw an exception while the parent datepicker or parent calendarpanel is being constructed , because a veto policy cannot be set until after the parent component is constructed .
