Improve loadMoreWidgetBuilder Behavior for minDate and maxDate Range Handling in Schedule View Scheduled

Current Behavior: 

When minDate and maxDate ranges are set near the end of the month, the loadMoreWidgetBuilder only triggers when the scroll offset reaches the end (top or bottom edge) of the schedule view and the appointment list fills or exceeds the visible screen height. If the initial appointments do not fill the view height, scrolling does not occur, and the load-more functionality is never called, resulting in appointments for the next month not loading.

Expected Behavior:

The schedule view should consistently load appointments for the next month when minDate and maxDate are set to include that range, regardless of scroll offset. The load-more functionality should work even when the initial appointments do not fill the view height, ensuring smooth navigation across months.

Use Cases:

• Android Platform:
  • Case 1: minDate = endOfMonth → Scrolling to December appointments does not work.
  • Case 2: minDate = oneDayBeforeEndOfMonth → Scrolling to December appointments works as expected.
• Windows Platform:
  • Case 1: minDate = endOfMonth → Only current month appointments load; scrolling to December does not work.
  • Case 2: minDate = oneDayBeforeEndOfMonth → Same behavior; only current month appointments load.
  • Reason: The load-more mechanism depends on scroll offset, and when initial appointments do not exceed the screen height, scrolling is not triggered, so loadMoreWidgetBuilder is never called.

Also, I have prepared the simple sample to replicate the issue by using the ClampingScrollPhysics. Kindly check it. 

Windows platform - The scroll does not happen with minimal list count - Have issue. 

Android platform - The scroll is trigger - No issue occurs.