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

WeekView events onEventTap does not get triggered for the current week. #329

Closed
ahmetakil opened this issue Mar 1, 2024 · 5 comments
Closed

Comments

@ahmetakil
Copy link
Contributor

When using the last version 1.1.0 and using a WeekView, when i add an event to this week's calendar so for instance yesterday or tomorrow,

onEventTap does not get called, but when i move the event to either next weeks calendar (For instance adding Duration of 6 days)
or to a previous weeks calendar (Removing duration of 7 days)

Then the onEventTap works as expected.

This issue does not happen if I rollback to version 1.0.4

DayView works fine as well so this seems to only effect the WeekView.

@Lingeshwaran78
Copy link

have you found the solution?

@ahmetakil
Copy link
Contributor Author

I'm using the version calendar_view: 1.0.4 which works as expected

@MaharGhazanfar
Copy link

When using the last version 1.1.0 and using a WeekView, when i add an event to this week's calendar so for instance yesterday or tomorrow,

onEventTap does not get called, but when i move the event to either next weeks calendar (For instance adding Duration of 6 days) or to a previous weeks calendar (Removing duration of 7 days)

Then the onEventTap works as expected.

This issue does not happen if I rollback to version 1.0.4

DayView works fine as well so this seems to only effect the WeekView.

This is because of Live time line indicator as if we set it for all days than event click alse not work for next week or previous week event like in current week. i have tried on previous version but the problem still exist.

@ahmetakil
Copy link
Contributor Author

There is a new commit on master branch that seems to fix this, I'm using that now that it's working as expected

Note as of now that is not live on pub.dev so you would need to reference the git repo directly

@apurva010
Copy link
Collaborator

Closing this issue as issue got fixed in #335.

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

4 participants