-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conflict with shouldSelectDate delegate call on future month #35
Comments
Try |
Still having the problem in 0.8.1. |
You sure? It works fine in the example. |
OK, I think I figured out what I did to cause the behavior. In your example code, I updated the code in
When I add this callback, the behavior I discuss above occurs. |
And what's the maximumDate? |
OK, that's how to make it work - make sure the minimumDate is the first day of month, and the maximumDate the last. I should've made it clear in Readme.Will fix it inside in next release. Thanks ~ |
I didn't have a maximum date but what you're saying makes sense. Thanks for the help! |
First of all let me say I love this control. Very well done. Best I've seen of the dozens of calendar controls out there.
I have implemented the
calendar:shouldSelectDate
delegate callback to prevent the user from selecting a date before today. The issue I'm having is that when the user selects one of placeholder cells for the next month, the delegate callback is not passing in the correct date.So, for example, given the month of June 2015, if the user selects the placeholder cell for July 1, I would expect the calendar to animate to the new month. However, what is happening is the wrong date is being sent to the delegate callback (it's actually sending June 3) which then causes my callback to return
NO
and the calendar never animates to the new month.I'm hoping I'm being clear. Let me know if you have any questions. Thanks again!
The text was updated successfully, but these errors were encountered: