lastSavedContentOffset not set on programmatic scroll

[KyleConway]

When using scrollToDate(...) or scrollToHeaderForDate(...) on a JTAppleCalendarViewCalendar, the initial value of lastSavedContentOffset remains 0 even when scroll animation has finished. As a result, the isScrollingForward flag within scrollViewWillEndDragging of UIScrollViewDelegate is being set incorrectly. This results in the calendar view bouncing back to its initial position on the first time the user scrolls to a previous month. It is 100% reproducible. On the next scroll attempt, the user is able to scroll correctly because the lastSavedContentOffset has been updated. It is the initial value of lastSavedContentOffset that needs to be calculated correctly after programmatic scroll.

[patchthecode]

Awesome nice find. Looking into it. Will approve this after i test it.
Thanks.

[KyleConway]

Thanks @patchthecode for the quick response - I should mention the use case for how I found this issue.

I have created a vertically enabled JTAppleCalendarView instance and I'm setting a starting date for the calendar to be a year prior to the current date and the ending date to be a year after. I am presenting my container controller as a modal and I want the calendar to open to the current date i.e. today.

Within viewWillAppear of my container controller, I am calling scrollToDate(...) on my instance of JTAppleCalendarView. Once opened, try to scroll to the previous month and it will bounce back to the original month every time.

After that it will work - only initially is the interaction failing for the previously mentioned reasons. I should also mention that scrolling mode = .stopAtEachSection too. Hope this helps - let me know if you need any more info.

[patchthecode]

Approved. Merged. Thanks again.