| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
This is a suggestion entry that does infix
matching, highlights the match, and sorts
the matches by relevance.
|
|
|
|
|
|
| |
Update the action enabledness when appropriate so
that an explicit button does not appear insensitive
when it shouldn't.
|
|
|
|
|
|
|
|
|
| |
Make it possible to use the suggestion entry
by doing filtering in the model yourself, and
set use-filter to FALSE. We are still getting
the popup behavior, but inserting prefixes
can't be guaranteed to work well if the
filtering isn't doing prefix matching.
|
|
|
|
|
| |
We shouldn't throw criticals when there is no
model. Just act like a plain entry.
|
| |
|
|
|
|
|
|
| |
Move the Dropdowns demo to Lists/Selections,
and make it show both GtkDropDown and
GtkSuggestionEntry, with some variations.
|
|
|
|
| |
A direct copy of GtkEntryCompletion:minimmum-key-length.
|
|
|
|
|
|
|
|
| |
This is useful for comboboxtext-like use cases.
To simulate comboboxtext behavior, set
use-filter = FALSE
show-button = TRUE
insert-selection = TRUE
|
|
|
|
|
|
| |
GtkSuggestionEntry is a replacement for GtkComboBoxText
and GtkEntryCompletion, very similar to GtkDropDown, but
using an entry as widget.
|
|\
| |
| |
| |
| | |
Ebassi/ci timeout
See merge request GNOME/gtk!2223
|
| |
| |
| |
| |
| |
| | |
Instead of an array of arrays, let's use an array of dictionaries; it's
easier to add optional keys without requiring to remember where to put
empty arrays.
|
| |
| |
| |
| | |
This increases the default timeout.
|
| |
| |
| |
| |
| | |
If a test is part of the 'slow' test suite, we should increment the
default timeout to compensate.
|
| |
| |
| |
| | |
We do have some slow tests.
|
| |
| |
| |
| | |
When running our test suite on our CI infrastructure.
|
|\ \
| |/
|/|
| |
| | |
ci: Use lsan again
See merge request GNOME/gtk!2224
|
| |
| |
| |
| |
| |
| | |
Turning it off didn't fix the crashes; and we allow
the asan build to fail anyway now. And the leak reports
are useful whenever it doesn't crash.
|
|\ \
| |/
| |
| |
| | |
Asan ci
See merge request GNOME/gtk!2214
|
| |
| |
| |
| |
| |
| |
| | |
The leak sanitizer causes on average 3-4 tests
to segfault during a testsuite run. Disable it
for now to see if we can get a successful
testsuite run with asan alone.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Run our testsuite under asan. We do this in a
separate build, since we need to turn off
introspection to make the build succeed.
As Michael Catanzaro pointed out, this requires a
privileged runner in order to use kernel apis.
|
| |
| |
| |
| |
| |
| |
| | |
These showed up in ci. The atk-bridge will
be gone before too long anyway. Since we
may not have debug symbols in ci, just at
the so's.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When running the testsuite with the address sanitizer,
many of our dependencies cause it to report cause it
to report memory leaks, causing tests to fail.
Therefore, point the leak sanitizer at a list of
suppressions. The list is kept in the lsan.supp
file in git.
|
| |
| |
| |
| | |
This image includes libasan and libubsan.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Add libasan and libubsan to fedora-base:v20,
and build fedora:20 on top of it.
This is so we can build and run the tests with
the address and undefined behavior sanitizers.
|
| |
| |
| |
| | |
Don't leak atoms when we're storing the clipboard.
|
|\ \
| | |
| | |
| | |
| | | |
build-aux: search various Glib/GIO utilities in .pc file.
See merge request GNOME/gtk!2129
|
| | |
| | |
| | |
| | |
| | |
| | | |
The pkg-config variables have been added in GLib 2.62.0. Let's fallback
to default names for these tools in such case (`pkg-config` still
returns a 0 return value, but with empty output for absent variables).
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Some distributions are renaming Glib/GIO utilities for multi-arch
reasons so pkg-config variables have been added to find the correct name
of a tool. GTK+ should use these variables instead of searching in PATH.
See glib#1796.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
x11: Plug a memory leak
See merge request GNOME/gtk!2222
|
|/ / /
| | |
| | |
| | | |
Don't leak atoms when we're storing the clipboard.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Wip/otte/for master
See merge request GNOME/gtk!2221
|
| | | |
| | | |
| | | |
| | | | |
It's too expsensive.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Create larger source models in tests, so that we hit the incremental
batch size more often and have a higher chance to expose bugs there.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Incremental filtering would skip every 513th element due to an
off-by-one error.
Test included
|
|\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | | |
gtkrange: group gestures the right way around
See merge request GNOME/gtk!2220
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The gtk_gesture_group() call is not a commutative operation, it
takes two gestures, maybe detaches the first one from its current
group, and adds it to the same group than the second gesture.
With the flipped argument order here, GtkRange was actually detaching
the same gesture in order to group it with a second one two times, so
the desired effect to group all 3 gestures was not achieved.
Fixes autoscroll as the drag gesture is now actually grouped with the
click one, so drag offsets can be accessed from the autoscroll
timeout.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
css: Plug a memory leak
Closes #2921
See merge request GNOME/gtk!2219
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When a rule has no styles, we don't add it
to our ruleset. Since we are not adopting
the selectors in this case, we must free them.
Fixes: #2921
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | | |
Scrollbar fixes
Closes #2879
See merge request GNOME/gtk!2216
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If we create an implicit grab on a surface, leave the surface, and
release the button, we would get 2 XI_Leave events, one with mode
XINotifyNormal when the pointer leaves the surface, and another with
mode XINotifyUngrab when the button is released.
Meanwhile, the upper layers rely on crossing events being paired,
and particularly in no crossing event being sent until the implicit
grab is dismissed (either by releasing it, or via more pervasive
grabs).
Ignoring the set of XINotifyNormal events while an implicit grab
is active adapts the X11 backend to this behavior. If the grab were
released or taken away by another grab, a crossing event with one
of the other XINotify*Grab/XINotify*Ungrab will be generated.
Fixes: https://gitlab.gnome.org/GNOME/gtk/-/issues/2879
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Check correctly that the captured motion events are emitted towards the
content or one of the scrollbars, in order to have it set the expected
"over" state depending on whether the drag begins from the scrolledwindow
content or one of the scrollbars.
Fixes: https://gitlab.gnome.org/GNOME/gtk/-/issues/2879
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Matthiasc/for master
See merge request GNOME/gtk!2212
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This can be used similar to valgrind suppressions:
LSAN_OPTIONS=suppressions=`pwd`/lsan.supp meson tests -Cbuild
|
| | | | |
| | | | |
| | | | |
| | | | | |
These showed up under asan.
|
| |/ / /
| | | |
| | | |
| | | | |
This showed up under asan.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Use depth=1 for cloning sub-projects
See merge request GNOME/gtk!2215
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We don't really need the full history and branches when building
sub-projects.
This should shave some bandwidth and time in our CI pipeline as well.
|
|\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
File chooser api cleanup 2
See merge request GNOME/gtk!2213
|