| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
pixbufutils: Remove an unused function
See merge request GNOME/gtk!3447
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
wayland: Don't duplicate xdg_surface setup code
See merge request GNOME/gtk!3191
|
| | |/ / / |
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
wayland: Avoid directly accessing shadow property of parent surface
See merge request GNOME/gtk!3190
|
| |/ / / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Fix builds against latest stable GLib with MSVC
See merge request GNOME/gtk!3443
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
GLib-2.68.x now considers warning C4098 ('void' function returning a value) as
an error, so avoid doing that.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
GLib-2.68.x now considers warning C4098 ('void' function returning a value) as
an error, so avoid doing that.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
GLib-2.68.x now considers warning C4098 ('void' function returning a value) as
an error, so avoid doing that.
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | | |
window: Fix deferred focus unsetting
Closes #3413
See merge request GNOME/gtk!3446
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In commit 4a76abffd4d62cbb, we deferred unsetting focus
and default until after the next draw, overlooking the
case where the focus is set to another widget before we
ever get to the unsetting.
Fixes: #3413
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
imcontext: Eat key events during preedit
See merge request GNOME/gtk!3440
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Avoid passing through random key press or release
events while we are showing preedit. That prevents
'accidents' like typing Ctrl-. bringing up the
Emoji chooser during preedit, or hitting Ctrl-a
after the Compose key moving the 'dot' around in
vim in terminals.
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
themes: Make fallback work a bit better
See merge request GNOME/gtk!3441
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
One case we did not include in fd329e0ec582d7562f444b is
Adwaita-dark -> Default:dark
It turns out that it is needed.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
meson: only build demo manpages when demos are enabled
See merge request GNOME/gtk!3438
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Installing them even when manpages are enabled, but the demos are
disabled, produces manpages for unavailable programs...
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
theme: Use -gtk-icon-filter for full-color icons
See merge request GNOME/gtk!1990
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Not for symbolic icons.
Don't apply `-gtk-icon-filter: opacity(0.5);` to the symbolic icons as
they already have the "gray" colors indicating the disabled state.
Symbolic icons can be styled using the `color` property.
Also remove the obsolete comment.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
x11: Be quiet on exit by default
See merge request GNOME/gtk!3436
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The condition we check for to catch X servers going away
may not be accurate anymore, and the warning shows up in
logs, causing customers to be concerned. So, be quiet by
default, unless the user explicitly asked for a message.
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | | |
ngl: Fix a rare assertion violation
Closes #3853
See merge request GNOME/gtk!3434
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When we clean up the uniform allocations after a frame,
it can happen that our space requirements actually increase,
due to padding that depends on the order of allocations.
Instead of asserting that it doesn't happen, just make
it work by growing our allocation.
Fixes: #3853
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
flatpak: Include highlight in gtk4-demo flatpak
Closes #3867
See merge request GNOME/gtk!3433
|
| | |/ /
| | |
| | |
| | |
| | |
| | | |
Include the highlight utility to make syntax
highlighting work in gtk4-demo. This requires
building its dependencies as well, boost and lua.
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
testsuite: Reduce the use of g_assert
Closes #3864
See merge request GNOME/gtk!3432
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Don't use -Wnull-dereference when assertions are
disabled, since that causes the compiler to see
NULL everywhere.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The gtk_debug_cflags variable is an array, with each argument stored in
a separate string; if we add multiple arguments inside the same string
we break the escaping rules.
Fixes: #3864
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Change all g_test_init calls in the testsuite
to avoid the macro, so they work regardless of
G_DISABLE_ASSERT.
|
| | | |
| | |
| | |
| | |
| | | |
The g_test_init macro 'helpfully' refuses to work when
assertions are disabled. So we just use the function.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
These happen for variables which are only used
in assertions, when assertions are disabled.
|
| | | |
| | |
| | |
| | | |
Avoid an unused variable warning.
|
| | | |
| | |
| | |
| | |
| | | |
Disabling assertions was provoking some unused variable
warnings from the compiler. Avoid these.
|
| | | |
| | |
| | |
| | | |
Stop using g_assert() in the gtk tests.
|
| |/ /
| |
| |
| | |
Stop using g_assert() in the gsk tests.
|
| |\ \
| | |
| | |
| | |
| | | |
Fix F16C build/runtime detection on Visual Studio
See merge request GNOME/gtk!3429
|
| | | |
| | |
| | |
| | |
| | |
| | | |
It is also possible to enable F16C instructions on 32-bit Visual Studio builds,
so also check for the compiler's ability to build F16C code on Visual Studio
32-bit instead of just bailing out.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We need to use __cpuid() to check for the presence of F16C instructions on
Visual Studio builds, and call the half_to_float4() or float_to_half4()
implementation accordingly, as the __builtin_cpu...() functions are strictly
for GCC or CLang only.
Also, since __m128i_u is not a standard intrisics type across the board, just
use __m128i on Visual Studio as it is safe to do so there for use for
_mm_loadl_epi64().
Like running on Darwin, we cannot use the alias __attribute__ as __attribute__
is also for GCC and CLang only.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
The __builtin_cpu...() intrisics are strictly for GCC/CLang-based compilers, so
don't use them in the checking code on Visual Studio. The test code will still
compile without this change, but will certainly fail if we want it to link.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
testsuite: Reduce use of g_assert
See merge request GNOME/gtk!3431
|
| | | |
| | |
| | |
| | | |
Stop using g_assert() in the css tests.
|
| | | |
| | |
| | |
| | | |
Stop using g_assert() in the reftests.
|
| | |/
| |
| |
| | |
Stop using g_assert() in the gdk tests.
|
| |\ \
| |/
|/|
| |
| | |
ngl: Fix outset blurred shadows
See merge request GNOME/gtk!3427
|
| | |
| |
| |
| | |
Ensure that we don't cut them off at the edges.
|
