-
Notifications
You must be signed in to change notification settings - Fork 272
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
Wrong date onDateTap when startHour != 0 #341
Comments
apurva010
added a commit
that referenced
this issue
Apr 30, 2024
- add startHour minutes (startHour * 60) to DateTime which then passed as arguments to onDateTap
7 tasks
apurva010
added a commit
that referenced
this issue
May 1, 2024
- add startHour minutes (startHour * 60) to DateTime which then passed as arguments to onDateTap
apurva010
added a commit
that referenced
this issue
May 1, 2024
- add startHour minutes (startHour * 60) to DateTime which then passed as arguments to onDateTap
7 tasks
apurva010
added a commit
that referenced
this issue
May 1, 2024
- add startHour minutes (startHour * 60) to DateTime which then passed as arguments to onDateTap
vatsaltanna-simformsolutions
pushed a commit
that referenced
this issue
May 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When startHour is set, onDateTap receives a wrong time.
The received time on the callback matches the index of the row on the view and not the actual hour, i.e., if you set a startHour of 9, the rendering is correct and the first hour on the calendar is 9. But if you tap the top of the day on DayView or WeekView - 9:00, the received time onDateTap is 0.
To fix this, before calling the callback the date must sum the defined startHour.
The text was updated successfully, but these errors were encountered: