Split onMonthChange() in 2 methods: 1) only onMonthChange listener 2) only events manager

[alamkanak]

Split onMonthChange() in 2 methods: 1) only onMonthChange listener 2) only events manager

[entropitor]

See this comment

Basically, the first time onMonthChange is called, you call your asyncTask.
When that's completed you save your events somewhere in your activity/fragment/... (somewhere where you can access them synchronously).
After saving the events you call mWeekView.notifyDatasetChanged();
This will trigger another round of onMonthChange() events. Now you have the data, so you can provide it in your return argument.

Notes: you should cache whether you're already loading the events for a specific month too. When the weekview is created, the previous, the current and next month will be loaded (in that order).
So when you call mWeekView.notifyDatasetChanged(); on the completion of the first request, the other 2 might not have finished and will be called again. (Basically, if you don't have this check, the current month will be loaded twice and the next month 3 times).

I suggest this issue to be left open as a reminder that we should update the readme with this explanation or at least a link to a wiki with a page of extra information for async loading.

[KimPark89]

Thank you, it works. And I agree with you for updating the readme. I think this is a pretty common problem.