| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
(cherry picked from commit c71d7a5a4fd2d06e2797a55750d5ce06caca1d25)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The only allowed child elements of `<p>` are `<em>` and `<code>`:
https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-description
Spotted in https://gitlab.gnome.org/GNOME/gnome-software/-/issues/2154
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
Fixes: #1012
|
|
|
|
| |
Fixes #954
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
The current compare function puts events closer to today at the end
of the list, instead of the beginning. Revert that.
|
|
|
|
|
|
|
| |
Now that we use a widget that appropriately handles infinite items,
we don't need to limit anything anymore.
Related: https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/624
|
| |
|
|
|
|
|
|
|
|
| |
When I originally wrote the code, I expected to create a new icon
every time that function was called. That expectation changed, but
the code wasn't fully updated.
Use g_value_set_object() instead of g_value_take_object().
|
|
|
|
|
|
| |
- Port the style to GTK4 and remove obsolete styles
- Fix double border in high contrast
- Update for libadwaita toolbar margin changes
|
|
|
|
|
| |
GtkComboBox is going to be deprecated in GTK 4.10.
This commit updates the "Repeat" rows in new schedule window to use AdwComboRow.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
When mapped, move focus to either the first meeting row - if any - or
to the edit button.
Closes https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/980
|
|
|
|
|
| |
We'll use this in the next commit to properly grab focus of the
first meeting row, if any.
|
|
|
|
| |
It's not necessary anymore.
|
|
|
|
| |
Helps: https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/980
|
|
|
|
|
|
| |
But child widgets are. That is, the Join button.
Helps: https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/980
|
|
|
|
| |
And bump the GTK dependency to 4.10
|
|
|
|
|
| |
I didn't realize these were translated, and accidentally broke string
freeze. Let's temporarily remove these strings for now.
|
| |
|
| |
|
|
|
|
| |
Cleans up a few more compiler warnings.
|
|
|
|
|
|
|
|
|
|
| |
The Month view is a complicated beast when it comes to allocating
events, but it's unnecessarily complicated since it tries to take
margins of events into accounts. With GTK4, that's not necessary
anymore, as GTK4 will independently and correctly apply margins
in widgets by itself, we don't have to do manually anymore.
Clean that up.
|
|
|
|
|
|
| |
Port the search results list to GtkListview. Use bindings to set
the title, icon, and subtitle of each row. Remove GcalSearchHitRow
as it's unused now.
|
|
|
|
| |
This allows not mixing up similar events from different calendars.
|
|
|
|
|
|
|
| |
Instead, monitor where items are added relative to each other, and
proxy the 'items-changed' call to match the inner list.
Helps https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/989
|
|
|
|
| |
It's a bit better than using -1 with an unsigned int :)
|
| |
|
|
|
|
|
|
|
|
| |
Quit the search entry state when the search entry emits stop-search,
usually that's when Escape is pressed when the search entry is
focused.
Closes https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/830
|
|
|
|
|
| |
It's, at best, annoying. Also stop resetting the entry text when
hiding suggestions, as it may loop with the text changed callback.
|
|
|
|
|
| |
It uses a 150ms delay, which helps with reducing the number of
queries we do.
|
| |
|
|
|
|
|
| |
Allows us to cleanup style a bit. Next commits will use search entry
functionality better.
|
|
|
|
|
| |
This might be the last reference to it, so keep it alive while
the signal is being emitted.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Search uses GcalTimeline, an object that is meant to be single
threaded, in multple threads. That mostly worked okay because
GcalTimeline mostly relies on GcalCalendarMonitor, which is
heavily threaded. But, sometimes it failed.
Rework that to be single-threaded, and asynchronous.
Closes https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/981
Closes https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/987
Closes https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/988
|