| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Failure to do so makes the old pointer focus target
'sticky', because we end up ignoring the result of
picking the pointer focus until a motion event comes
in.
Fixes: #3172
|
|
|
|
|
|
|
|
|
| |
Redo the tag insertion function to avoid quadratic
behavior, and at the same time, fix handling of
alpha for color attributes.
Update the copy of this function in gtk4-demo
as well.
|
|\
| |
| |
| |
| |
| |
| | |
Radial gradients
Closes #2262, #3170, and #3173
See merge request GNOME/gtk!2597
|
| | |
|
| |
| |
| |
| | |
Fixes #3173
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
These are the equivalents of the linear gradient apis.
|
| |
| |
| |
| |
| |
| | |
Only a fallback implementation for now.
Fixes #2262
|
|\ \
| | |
| | |
| | |
| | | |
fontchooser: add language filtering
See merge request GNOME/gtk!2551
|
| | |
| | |
| | |
| | |
| | | |
Avoid ordering issues in dispose by disconnecting
the rows_changed_cb handler first thing.
|
| | |
| | |
| | |
| | |
| | | |
Don't switch to the empty page while we are still busy
filtering. Fonts might yet appear.
|
| | |
| | |
| | |
| | |
| | |
| | | |
When you are asking to only see fonts that support
a given language, you probably want to see the
sample text for that language too.
|
| | |
| | |
| | |
| | |
| | | |
Add a popover that has filtering options. As a start,
allow filtering by monospace and by language coverage.
|
| | |
| | |
| | |
| | |
| | | |
Shorten a few of the names we pick up by removing
parentheses that make them excessively long.
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
win32: Fix compiler warnings
See merge request GNOME/gtk!2596
|
| |/
| |
| |
| |
| | |
The compiler informs me that GetLastError() return a DWORD,
so use %lx to print it.
|
|/
|
|
|
|
|
|
|
| |
Look at the languages supported by a font, and pick
a suitable sample text from the pango list of sample
texts. We can only implement this on platforms using
fontconfig, since it relies on pangofc apis.
This bumps the pango dependency to 1.47.1.
|
|
|
|
|
| |
It's NULL anyway, so freeing GError with g_free() when it's allocated with
GSlice never actually happens, but it just looks bad.
|
|
|
|
|
|
|
|
|
|
|
| |
When we remove anchors with widgets from the text
buffer, we used to call gtk_widget_destroy(), which
indirectly called gtk_container_remove() which cleared
the child properly. When gtk_widget_destroy() was
removed, we replaced the calls with gtk_widget_unparent(),
but that is not enough. Explicitly call
gtk_text_view_remove() instead - we know the parent
is a text view.
|
|
|
|
|
| |
We were claiming the clicks too eagerly, preventing
clickable links, e.g. in GtkAboutDialog, from working.
|
|
|
|
|
|
|
| |
gtk_show_uri() not freeing the error after showing
it to the user.
Pointed out by Peter Bloomfield in #3166
|
|
|
|
|
|
|
| |
The name of children is not essential, so add
a way to add children without providing one.
Fixes: #3165
|
|\
| |
| |
| |
| |
| |
| | |
Adwaita: update tango color for DND
Closes #3158
See merge request GNOME/gtk!2581
|
| |
| |
| |
| | |
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/3158
|
|\ \
| | |
| | |
| | |
| | | |
Matthiasc/for master
See merge request GNOME/gtk!2582
|
| |/
| |
| |
| |
| |
| | |
Using gtk_widget_insert_before on a complex container
is a *bad* idea; it will mess up the containers bookkeeping
of its children and can easily lead to failure and crashes.
|
| | |
|
| |
| |
| |
| |
| |
| | |
Quickly clicking rows should always activate the row if
single-click-activation is enabled. Before, only the first click
(n_press == 1) would activate the row.
|
| | |
|
| |
| |
| |
| | |
g_list_store_append refs the file
|
| | |
|
| | |
|
|/
|
|
| |
This is handled by .rich-list
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While it's a bit dubious whether array+length annotations should be
marked as "nullable", we do this elsewhere in the API, so might as well
be consistent.
In practice, the array argument is only ever allowed to be NULL iff the
length argument is 0; annotations are static, so if somebody decides to
pass a NULL argument with a non-zero value, they will get a run time
critical error, instead of a compile time one, which is somewhat counter
to the point of annotating the API in the first place.
Fixes: #2923
|
|\
| |
| |
| |
| | |
Adwaita: navigation list expander whitespace
See merge request GNOME/gtk!2575
|
| |
| |
| |
| | |
- Address https://gitlab.gnome.org/GNOME/gtk/-/issues/3138#note_910476
|
|/
|
|
|
|
|
| |
- separate labels
- 12px margins around cells
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/3164
|
|\
| |
| |
| |
| |
| |
| | |
Wip/jimmac/natigation sidebar whitespace
Closes #3138
See merge request GNOME/gtk!2572
|
| |
| |
| |
| |
| |
| | |
- split from placessidebar as it's more generic
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/3138
|
|/
|
|
|
|
| |
- quick, somebody on the internet is offended!
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/3074
|
| |
|
|
|
|
|
| |
Mode all the debug flags related code together,
to make gtkmain.c a bit less messy.
|
|
|
|
|
| |
This environment variable is undocumented, and you can
just use GTK_DEBUG=touchscreen insead.
|
|
|
|
|
| |
This is just an internal cleanup, to make gtkmain.c
a bit less messy.
|
|
|
|
| |
Use the GtkDebugFlags enum, since we have it.
|
| |
|
|
|
|
| |
The function does not exist.
|