Skip to content
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

Does not work well when scrolling across months (after dismissing once) #40

Open
hightitude opened this issue Sep 13, 2014 · 3 comments

Comments

@hightitude
Copy link

A few issues :

  1. On clicking the button the calendar gets displayed, but the user is unable to click the button again (as the button is hidden behind, or disabled or something).
  2. If the calendar is being displayed and i use a background tap to dismiss it, then on clicking the calendar again and moving across months causes the calendar to display incorrectly (see image).

// Dismiss the keyboard and calendar when the background is tapped

  • (IBAction)backgroundTap:(id)sender
    {
    [self.pmCC dismissCalendarAnimated:NO];
    }

pmcalendar-bug

@hightitude
Copy link
Author

Actually I don't think it has anything to do with the gesture recognizer. On clicking anywhere outside of the calendar to dismiss the calendar and then showing the calendar again and switching months causes this issue.

@hightitude hightitude changed the title Does not work well with Tap Gesture recognizer Does not work well when scrolling across months (after dismissing once) Sep 13, 2014
@Endareth
Copy link

I initially ran into this graphical bug as a result of setting period on the calendar controller before presenting it. After seeing this issue I was able to trigger the same bug by dragging to select across months, and I'm betting it's the same root cause. If I get the chance I'll going to try and debug it. Until then, I'm just avoiding setting the initial period value when using the calendar, and hope the user doesn't notice the problem! 😉
As this seems to be the only multi-selectable calendar control around, I hope there's an easy fix for it.

@hightitude
Copy link
Author

"I'm just avoiding setting the initial period"... How ? I haven't set the period initially. By default the current date is set on the calendar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants