utils: Make date comparison follow time comparison semantics
Right now, comparing dates with gcal_date_time_compare_date() gives the exact opposite result of when comparing using g_date_time_compare(). As shown by this patch, this was a source of *many* bugs.
This commit is contained in:
@@ -1890,8 +1890,8 @@ gcal_event_is_within_range (GcalEvent *self,
|
||||
|
||||
if (gcal_event_get_all_day (self))
|
||||
{
|
||||
return gcal_date_time_compare_date (range_end, event_start) < 0 &&
|
||||
gcal_date_time_compare_date (range_start, event_end) > 0;
|
||||
return gcal_date_time_compare_date (range_end, event_start) > 0 &&
|
||||
gcal_date_time_compare_date (event_end, range_start) > 0;
|
||||
}
|
||||
|
||||
return g_date_time_compare (range_end, event_start) > 0 &&
|
||||
|
||||
Reference in New Issue
Block a user