You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there is a date that ends on the last day of the week based on the calendar, the event widget is drawn for another week (for this screenshot, it's Saturday)
The _mapSimpleEventToDrawerOrNull function in the event_util.dart file determines the scope of the event widget, which seems to have caused a bug.
In this function, the code part below is the part that handles exceptions, but it does not appear to be properly handled.
So as a temporary measure, I'll get rid of unit parameters
if (jEnd.isBefore(begin) ||
jBegin.isAfter(end)) {
return null;
}
If you make it into , the bug disappears.
Please check if the solution I solved is right.
If this is not a solution, I would like you to tell me the role of the unit parameter.
The three screenshots above are the screens with bugs.
The event widget exists until July 1, but the actual event only exists until June 24.
After fixing the code, the bug disappeared like this.
The text was updated successfully, but these errors were encountered:
jihanga
changed the title
I think I found a bug in the _mapSimpleEventToDrawerOrNull function in the event_util.dart file
event widget range bug
Jun 21, 2023
jihanga
added a commit
to jihanga/cr_calendar
that referenced
this issue
Jun 21, 2023
In my opinion, we can either wait for Jiffy to evaluate and release a fix or switch to a custom compare logic. I can open a pull request for the latter if needed.
If there is a date that ends on the last day of the week based on the calendar, the event widget is drawn for another week (for this screenshot, it's Saturday)
The
_mapSimpleEventToDrawerOrNull
function in theevent_util.dart
file determines the scope of the event widget, which seems to have caused a bug.In this function, the code part below is the part that handles exceptions, but it does not appear to be properly handled.
So as a temporary measure, I'll get rid of unit parameters
If you make it into , the bug disappears.
Please check if the solution I solved is right.
If this is not a solution, I would like you to tell me the role of the
unit
parameter.The three screenshots above are the screens with bugs.
The event widget exists until July 1, but the actual event only exists until June 24.
After fixing the code, the bug disappeared like this.
The text was updated successfully, but these errors were encountered: