- Nov 03, 2020
-
-
Alice Mikhaylenko authored
- Oct 30, 2020
-
-
Alice Mikhaylenko authored
We don't have that version of gdk-pixbuf in amber, so keep carrying the patch. This reverts commit 95d5bd11.
-
Alice Mikhaylenko authored
-
-
- Oct 05, 2020
-
-
Simon McVittie authored
-
- Sep 26, 2020
-
-
Simon McVittie authored
This ensures that they are updated even if upstream forgot to do so, as happened in HighContrast for the GTK 3.4.22 release (#970664).
-
- Sep 11, 2020
-
-
Iain Lane authored
-
- Sep 10, 2020
- Sep 03, 2020
-
-
Matthias Clasen authored
-
Fabio Tomat authored
-
- Sep 02, 2020
-
-
Emmanuele Bassi authored
[3.24] Annotate sequence argument of GtkGesture signals as nullable See merge request GNOME/gtk!2521
-
Sebastian Dröge authored
-
Balázs Meskó authored
-
Balázs Meskó authored
-
- Sep 01, 2020
-
-
Matthias Clasen authored
searchengine: Prepare for apps linking to Tracker 2.x See merge request GNOME/gtk!2513
-
Asier Sarasua Garmendia authored
-
Carlos Garnacho authored
Given it does seem likely Tracker is going to miss the goal to get all applications ported to Tracker 3, the scenario where there's applications linking to Tracker 2.x while GTK was built with Tracker 3 support becomes more likely. Avoid the upcoming GType clashes if that were the case, and resort to the good (I lie) old Tracker 2 search engine.
-
- Aug 31, 2020
-
-
Matthias Clasen authored
gdk: Keep a reference on the last source device See merge request GNOME/gtk!2510
-
sicklylife authored
-
Carlos Garnacho authored
This device may go away, which means we have a pointer to a possibly stale object. Keep a reference here, and let future events bring this accounting up-to-date when the mouse pointer is next updated via other device. Fixes: https://gitlab.gnome.org/GNOME/gtk/-/issues/855
-
Matthias Clasen authored
Fix resource leak in gdk_display_close() under Wayland See merge request GNOME/gtk!2508
-
Julien Ropé authored
When using the gdk_display_close(), the handle to the Wayland compositor was not released. This could cause the consumption of all available handles, preventing other processes from accessing the display. Fixing this by calling wl_display_disconnect() when releasing the GdkWaylandDisplay object. Signed-off-by: Julien Ropé <jrope@redhat.com>
-
- Aug 29, 2020
-
-
Boyuan Yang authored
-
Changwoo Ryu authored
-
Changwoo Ryu authored
-
- Aug 28, 2020
-
-
Jiri Grönroos authored
-
- Aug 26, 2020
-
-
Matthias Clasen authored
wayland: Fix dnd hotspot movement See merge request GNOME/gtk!2491
-
Matthias Clasen authored
Look up font and mouse settings in gsettings-desktop-schemas (3.24) See merge request GNOME/gtk!2490
-
Alexander Mikhaylenko authored
_gdk_wayland_window_offset_next_wl_buffer() moves the window relatively to its current position, pass it a delta instead of new position.
-
Carlos Garnacho authored
Handle both these settings, and the older settings-daemon ones for backwards compatibility. The keys are already checked for existence in the schema, so it will just use the existing ones.
-
Carlos Garnacho authored
Prefer this location, but also look for the old location in settings-daemon for backwards compatibility. This applies to both direct settings lookups and via the settings portal.
-
- Aug 25, 2020
-
-
Nathan Follens authored
-
Nathan Follens authored
-
- Aug 23, 2020
-
-
Juliano de Souza Camargo authored
-
Juliano de Souza Camargo authored
-
Goran Vidović authored
-