diff options
| author | Georges Basile Stavracas Neto <georges.stavracas@gmail.com> | 2023-03-17 14:27:51 -0300 |
|---|---|---|
| committer | Georges Basile Stavracas Neto <georges.stavracas@gmail.com> | 2023-04-22 10:22:57 +0000 |
| commit | 7b68931973e3c82576c9c858524579d947e65529 (patch) | |
| tree | ad29eb0c38867df20dfb3fcf87d17e54e42e6dab | |
| parent | d7b2a7d88ca0af1a3f5a525843f5703b8b60ebd5 (diff) | |
| download | gnome-calendar-7b68931973e3c82576c9c858524579d947e65529.tar.gz | |
search/engine: Increase range to a whole year
This is still not the ideal solution, but now that we have widgetry
that can handle hundreds of thousands of events, no limitations to
the maximum number of events, and no crashes related on the search
engine, we can increase the search range to a broader value and
show more results.
Helps: https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/624
| -rw-r--r-- | src/search/gcal-search-engine.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/search/gcal-search-engine.c b/src/search/gcal-search-engine.c index 87cd7d46..c4ee4370 100644 --- a/src/search/gcal-search-engine.c +++ b/src/search/gcal-search-engine.c @@ -225,8 +225,8 @@ gcal_search_engine_search (GcalSearchEngine *self, timezone = gcal_context_get_timezone (self->context); now = g_date_time_new_now (timezone); - range_start = g_date_time_add_weeks (now, -1); - range_end = g_date_time_add_weeks (now, 3); + range_start = g_date_time_add_months (now, -6); + range_end = g_date_time_add_months (now, 6); model = gcal_search_model_new (cancellable, range_start, range_end); gcal_timeline_set_filter (self->timeline, search_query); |