| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
We don't differentiate between foreground and backdropped selections,
which confuses/infuriates users, particularly in the FileChooser entry.
There's no design desire to introduce that differentiation in the theme.
The preferred fix is instead to clear the selection on focussing out.
This patch does that by changing the existing code that clears the
selection when the state changes and the widget is no longer :sensitive
to instead clear the selection if it's not the focus within its toplevel
https://gitlab.gnome.org/GNOME/gtk/issues/665#note_110313
|
| |
|
|
|
|
| |
See https://developer.gnome.org/hig/stable/typography.html
https://bugzilla.gnome.org/show_bug.cgi?id=772371
|
| |\
| |
| |
| |
| | |
Remove some duplication in testfilechooserbutton
See merge request GNOME/gtk!342
|
| | |
| |
| |
| |
| |
| |
| | |
Most of the code creating the two types of dialogs (open file,
choose folder) is the same. This refactors the common code into a
helper method. This also makes it easier to add other chooser types
for this test (e.g. save file).
|
| |\ \
| | |
| | |
| | |
| | | |
Get GTK+ 4 installed-tests closer to working
See merge request GNOME/gtk!348
|
| | | |
| | |
| | |
| | |
| | |
| | | |
The installed-tests want to run this.
Signed-off-by: Simon McVittie <smcv@debian.org>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
The executable is called autotestkeywords, so we shouldn't try to run
an executable named keywords. Also rename the metadata file to match.
Signed-off-by: Simon McVittie <smcv@debian.org>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
The installed-tests are now namespaced as gtk-4.0 to avoid colliding
with GTK+ 3, but these files weren't updated.
Signed-off-by: Simon McVittie <smcv@debian.org>
|
| | | | |
|
| | | | |
|
| |/ / |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
After removing elements, there were a few cases where the tree wasn't
properly balanced which could further down violate assumptions about the
layout.
Attached is the original testcase that triggered it. I didn't bother
simplifying it.
|
| |\ \
| | |
| | |
| | |
| | | |
GDK W32: send both smooth and discrete scrolling events (GTK4)
See merge request GNOME/gtk!337
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Commit 359df028be7b1dae76a1abb9bad8a3b86a648765 changed the
code to send GDK_SCROLL_SMOOTH with deltas instead of
GDK_SCROLL_(UP|DOWN|LEFT|RIGHT).
Windows defines deltas inversed for vertical direction
(positive values mean the wheel was turned forward)
but not for horizontal direction
(positive values mean the wheel was turned towards the right).
This commit fixes behavior as both axes were inverted previously.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Commit d64467b33475bf8358f66bec9450101f37c05e9c changed the
code to send GDK_SCROLL_SMOOTH with deltas instead of
GDK_SCROLL_(UP|DOWN|LEFT|RIGHT). Change it again, to send
both the GDK_SCROLL_SMOOTH and the GDK_SCROLL_(UP|DOWN|LEFT|RIGHT)
event separately (with the discrete event marked as emulated),
as this is what other backends (such as wayland) do.
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
gtkrevealer: support minimum size of child
Closes #635
See merge request GNOME/gtk!317
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Up until now when allocating the child it only used the natural size
while the measuring also used the minimum size, resulting in a clipped
child when animating if the child had different minimum size and
natural size. This was an obvious case when using labels that had
ellipsization.
This commit gives full allocation to the child by inverting the size
the revealer reduces from its animation progress.
Code done by Benjamin Otte.
Closes: https://gitlab.gnome.org/GNOME/gtk/issues/635
|
| | |
| |
| |
| | |
This was requested on IRC; the docker image in the registry is updated already.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
The complexity with model items vs row items is really confusing. Add to
that treelistmodel position vs child model position vs parent position,
and you're so confused, even the best naming can't help.
And once you're there, consider passthrough vs non-passthrough...
|
| | |
| |
| |
| | |
Fixes #1341
|
| | |
| |
| |
| |
| |
| | |
This reverts commit 03679d434262be5a73e25668513a6a6597fd90ea.
listlistmodel is private
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When passthrough is enabled, it should return the GType
of the child GListModels; when disabled, it should be
GTK_TYPE_TREE_LIST_ROW.
The conditions are inverted however, causing a few
warnings to trigger.
Fix that by returning the correct GType.
|
| |\ \
| | |
| | |
| | |
| | | |
treelistmodel: Fix memory leak
See merge request GNOME/gtk!344
|
| |/ /
| |
| |
| |
| |
| | |
gtk_tree_list_model_init_node() increases the reference count
of the model passed. Let's not do that, and let it take the
model passed.
|
| |\ \
| |/
|/|
| |
| | |
treelistmodel: Fix signal emission on row destroy
See merge request GNOME/gtk!343
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| | |
toolbar: Use hexpand/vexpand Gtk+ properties
See merge request GNOME/gtk!334
|
| |/ |
|
| | |
|
| |
|
|
| |
Clarify some wording.
|
| | |
|
| | |
|
| |
|
|
| |
We were adding items in reverse order, oops.
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
gdkselectioninputstream-x11: Fix memory leak
See merge request GNOME/gtk!340
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Now we show all the controllers that are relevant when widget gets sent
events.
|
| | |
| |
| |
| |
| | |
Now display how many items were filtered (if any) and how many
directories remain to be sanned (if any).
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Add a simple search that does a case insensitive substring search of the
file paths.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is way more complicated than it should be, because it requires
manually limiting the number of open file enumerators.
On the other hand, it exhaustively tests the items-changed emission of
all involved listmodels because those signals come in pretty much
randomly.
It's also 50% slower than the sync version, with the caeat that the sync
version only shows the UI after it's done loading, while this version
shows it right away.
|
| | |
| |
| |
| | |
... and make the lists long by autoexpanding the tree.
|
| | | |
|
| | | |
|
