| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Some locations have to be mounted, but their mounts are not user-visible
(e.g. smb-browse). Though this is maybe a bit weird, it is how it works
for years. The problem is that the commit 267ea755, which tries to get the
default location for opening, caused regression as it doesn't expect such
possibility. Before this commit, such locations were opened without any
issue, but nothing happens currently after clicking to "Connect" except of
clearing the "Connect to Server" entry. Let's fallback to the original
location if the mount was not found to fix this regression.
Fixes: https://gitlab.gnome.org/GNOME/nautilus/-/issues/1811
|
| |\
| |
| |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| |
| | |
When the corners are too big to make slicing work,
don't do it, since it leads to broken results.
|
| | |
| |
| |
| |
| | |
In the non-sliced case, we were rendering the shadow
upside down.
|
| | |
| |
| |
| | |
This can be helpful in understanding shadow bugs.
|
| |\ \
| | |
| | |
| | |
| | | |
togglebutton: Fix expected group behavior
See merge request GNOME/gtk!3425
|
| | |/
| |
| |
| |
| |
| |
| | |
The expectation is that a grouped button stays
active when you click it. Grouped check buttons
behave this way, and grouped toggle buttons should
too.
|
| |\ \
| | |
| | |
| | |
| | | |
gsk: Don't overshadow
See merge request GNOME/gtk!3419
|
| | | |
| | |
| | |
| | | |
Reduce the cairo shadows to the same size as their GL brethren.
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
menubutton: Propagate focus-on-click
See merge request GNOME/gtk!3424
|
| | | |
| | |
| | |
| | |
| | | |
This is rarely useful, and is confusing when it
happens as side-effect of dragging the window.
|
| | | |
| | |
| | |
| | |
| | | |
This is rarely useful, and is confusing when it
happens as side-effect of dragging the window.
|
| | | |
| | |
| | |
| | |
| | | |
This is rarely useful, and is confusing when it
happens as side-effect of dragging the window.
|
| | | |
| | |
| | |
| | |
| | | |
This is rarely useful, and is confusing when it
happens as side-effect of dragging the window.
|
| |/ /
| |
| |
| |
| |
| |
| |
| | |
Propagate the focus-on-click setting to the button
inside, so that setting menubuttons as !focus-on-click
works as expected. This helps for menubuttons in
header bars, where dragging on the button will otherwise
steal focus from the content.
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
some small optimizations
See merge request GNOME/gtk!3423
|
| | | |
| | |
| | |
| | |
| | |
| | | |
update_clip only uses the bounds of the node that
we are currently passing. This opens the door to
updating the clip while handling a single node.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
When 9-slicing shadows, omit the center tile when it is
entirely contained in the outline (that is not always
the case, depending on corners and offsets).
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
gsk_rounded_rect_contains_rect was calling
gsk_rounded_rect_contains_point, which potentially
checks all four corners, for a total of up to 16
corner/point checks. But there is no need to do
more than 4 such checks to answer the question.
|
| | | |
| | |
| | |
| | | |
We really want equality here.
|
| |/ /
| |
| |
| |
| | |
Make the help window wide enough to show the
tables without wrapping.
|
| |\ \
| | |
| | |
| | |
| | | |
media: Fix a memory leak
See merge request GNOME/gtk!3420
|
| | | |
| | |
| | |
| | | |
This was introduced in e7dc82fa32f9c115607.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
window: Defer focus setting until after paint
Closes #3725
See merge request GNOME/gtk!3417
|
