- 25 Jan, 2021 2 commits
-
-
Matthias Clasen authored
Adwaita: make scrollbars larger See merge request !3110
-
Jakub Steiner authored
When using scrollbars as active controls, rather than their primary role as indicators, increase their size as click targets. Fixes #1886
-
- 21 Jan, 2021 1 commit
-
-
Fabio Tomat authored
-
- 18 Jan, 2021 4 commits
-
-
Bruce Cowan authored
-
Jordi Mas authored
-
Matthias Clasen authored
Allow GTK_DEBUG=interactive even without G_ENABLE_DEBUG defined See merge request !3090
-
Vanadiae authored
Currently when GTK3 is compiled without G_ENABLE_DEBUG, the inspector can't be opened with GTK_DEBUG=interactive because it doesn't parse this env var without G_ENABLE_DEBUG. Since the inspector is always good to have, this commit now always parses the GTK_DEBUG env var but only keep the "interactive" flag if G_ENABLE_DEBUG isn't defined.
-
- 16 Jan, 2021 1 commit
-
-
Марко М. Костић (Marko M. Kostić) authored
-
- 14 Jan, 2021 2 commits
-
-
Matthias Clasen authored
gdk/wayland: Mark matched settings from the portal as valid (3.24) See merge request !3077
-
Carlos Garnacho authored
Commit e6209de9 added some checks on TranslationEntry.valid in order to figure out whether using the new font settings or the old g-s-d ones. However that's only set in the non-sandboxed case. This makes sandboxed applications fallback to the old (and also non-existing with modern g-s-d) settings, possibly resulting in ugly defaults being picked. Fix this by also marking TranslationEntry elements as valid when using the settings portal, precisely those entries that we are able to read and match with our own table.
-
- 10 Jan, 2021 2 commits
-
-
Carlos Garnacho authored
Wayland: Fix segfault when receiving tablet/touch events for surfaces that have already been destroyed client-side See merge request !2809
-
Benedikt Ames authored
When destroying a wl_surface (e.g. when a window or menu is closed), the surface may continue to exist in the compositor slightly longer than on the client side. In that case, the surface can still receive input events, which need to be ignored gracefully. In particular, this prevents segfaulting on wl_surface_get_user_data() in that situation. Reported in #3296 The same issue for pointers/keyboards was reported in https://bugzilla.gnome.org/show_bug.cgi?id=693338 and fixed with in bfd7137f 3625f178 a8fc099a
-
- 06 Jan, 2021 3 commits
-
-
Carlos Garnacho authored
wayland: avoid set_cursor() when unchanged or invisible See merge request !2822
-
Matthias Clasen authored
gdkglcontext-win32.c: Workaround Intel glBlitFramebuffer() issues See merge request !2996
-
Matthias Clasen authored
fix touchscreen events processing in broadway.js See merge request !2972
-
- 04 Jan, 2021 1 commit
-
-
Fran Dieguez authored
-
- 31 Dec, 2020 1 commit
-
-
Fabio Tomat authored
-
- 28 Dec, 2020 1 commit
-
-
Chun-wei Fan authored
The autotools pattern rules can be off-putting...
-
- 27 Dec, 2020 2 commits
-
-
Zmicer Turok authored
-
Zmicer Turok authored
-
- 24 Dec, 2020 5 commits
-
-
Chun-wei Fan authored
It turns out that we must put Directory.Build.props in win32/vs10 and let automake copy it over to win32/vs15/... so do that, and only dist the copy in win32/vs15.
-
Chun-wei Fan authored
We need to account for the lack of Directory.Build.props in win32/vs10...
-
Chun-wei Fan authored
Update the NMake Makefiles used for generating the various sources be able to cope with an ARM64 build environment, and update the project files, in particular for Visual Studio 2017 (VisualStudioVersion 15.0) so that we can pull in the system .lib's that were somehow excluded from the default list on ARM64 builds. Also, add a custom Directory.Build.props in win32/vs15 so that we do not try to build with the Windows 8.1 SDK by defualt, which is not ready for ARM64 builds, but instead uses the appropriate Windows 10 SDK that supports this. Update the README.win32 file to give people instructions on how ARM64 builds can be carried out.
-
Chun-wei Fan authored
Look in the include/harfbuzz directory that is under the pre-defined prefix directory, as Pango 1.44.x and later pulled in HarfBuzz headers for all builds
-
Chun-wei Fan authored
Instead, use the $(GDBUS_CODEGEN) NMake Makefile variable, so that it may be overridden if needed
-
- 23 Dec, 2020 6 commits
-
-
Danial Behzadi authored
-
Emmanuele Bassi authored
Fix gtk-3-24 builds on older C89-esque compilers See merge request !2995
-
Chun-wei Fan authored
Intel OpenGL drivers have an issue where the results of a series of glBlitFramebuffer() can delay updating the display, when we use GDK_GL=always, which is manifested when attempting to enter text in text boxes. This attempts to work around this issue by requiring a glFlush() call and a retry to the same glBlitFramebuffer() calls to avoid delays in keystrokes when using GDK_GL=always and when not using libANGLE OpenGL/ES emulation, when an Intel OpenGL driver is being used. Special thanks to Lukas K. for the analysis and coming up with a workaround, which this patch builds upon. Fixes issue 3487
-
Chun-wei Fan authored
fmin() is a function that is introduced with C99/C++11, so check for the presence of it and provide a simple implementation for it if it does not exist. Also update the config.h.win32.in template accordingly, since this function is provided on Visual Studio 2013 or later.
-
Chun-wei Fan authored
This way, the code can be built on C89-esque compilers.
-
Chun-wei Fan authored
This way, we can enable the built binaries to print out diagnostic messages as needed by the values we set via the envvar GDK_DEBUG. The release configs of the Visual Studio project files follow the settings of Meson's `debugoptimized` build settings.
-
- 21 Dec, 2020 1 commit
-
-
Matthias Clasen authored
Cursor aspect ratio fixes for gtk 3 See merge request !2965
-
- 20 Dec, 2020 2 commits
-
-
sicklylife authored
-
sicklylife authored
-
- 18 Dec, 2020 1 commit
-
-
Maxim Zakharov authored
Makes event listeners active explicitly if supported; corrects handling for deleted surfaces preventing javascript errors in accessing deleted objects; makes event identifiers unique for broadwayd when executing in Chrome on Android. Partially fixes #1493
-
- 16 Dec, 2020 3 commits
-
-
Sebastian Keller authored
The size of the cursor depends on either the gtk-cursor-aspect-ratio GtkSetting or as of the previous commit on the GtkSetting or the cursor-aspect-ratio style property. GtkTextView was only considering the style property. Related: #3441
-
Sebastian Keller authored
The gtk-cursor-aspect-ratio GtkSetting was only recently introduced and replaced the cursor-aspect-ratio style property. This was causing old configurations that used CSS to modify this property to no longer apply. This commit introduces a fallback from the GtkSetting to the style property if the value of the setting is unchanged. Related: #3441
-
Sebastian Keller authored
The gtk-cursor-aspect-ratio property got added as a float property. However there is no parser for float values from keyfiles which meant that it could not be changed from settings.ini. Fixes #3441
-
- 14 Dec, 2020 2 commits
-
-
Emmanuele Bassi authored
gdkpixbuf-drawable: Free the pixbuf on Cairo error See merge request !2952
-
Adrien Plazas authored
This avoids leaking the pixbuf.
-