| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit e6209de9625 added some checks on TranslationEntry.valid in
order to figure out whether using the new font settings or the
old g-s-d ones. However that's only set in the non-sandboxed case.
This makes sandboxed applications fallback to the old (and also
non-existing with modern g-s-d) settings, possibly resulting in
ugly defaults being picked.
Fix this by also marking TranslationEntry elements as valid when
using the settings portal, precisely those entries that we are able
to read and match with our own table.
|
|\
| |
| |
| |
| | |
Matthiasc/for master
See merge request GNOME/gtk!3075
|
| |
| |
| |
| |
| | |
One of the many migration guide sections was too
prominent.
|
|/
|
|
|
|
| |
Don't mention GdkSurface::layout as replacement for
GtkWindow::configure-event. Instead, explain how to
save window state.
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Support stylus devices on macos
See merge request GNOME/gtk!3058
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
Ebassi/aspect frame doc
See merge request GNOME/gtk!3073
|
| | |
| | |
| | |
| | |
| | | |
The GtkAspectFrame:ratio getter will return the value set, not the
actual ratio computed in case GtkAspectFrame:obey-child is TRUE.
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
dist: Add a dist script to generate css
See merge request GNOME/gtk!3074
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
When I added the sassc option, I failed to ensure that
the theme css is included in the tarballs. This is required
to make tarball builds with -Dsassc=disabled work.
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
a11y: Fix leak
See merge request GNOME/gtk!3072
|
|/ /
| |
| |
| | |
Introduced by me in commit 03b60a2d5e40da1b137117aba05a2c818edd09b3.
|
|\ \
| | |
| | |
| | |
| | | |
a11y: Sanitize the AT-SPI object path further
See merge request GNOME/gtk!3071
|
| |/
| |
| |
| |
| |
| | |
When falling back to g_get_prgname(), we need to take into account that
the program name may be the full argv[0] path, which will end up messing
the DBus object path.
|
|\ \
| | |
| | |
| | |
| | | |
About dialog icon size
See merge request GNOME/gtk!3070
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When the icon size changes, we want to reload themed
icons.
This was showing up as the GtkImage in about dialogs
getting a big size with the same small icon upon
changing -gtk-icon-size in the inspector.
|
| | |
| | |
| | |
| | |
| | | |
Use 128 as the icon size for the image widget
in about dialogs.
|
| | |
| | |
| | |
| | | |
Make it explicit that we want large icons here.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Add the .aboutdialog style class to toplevel
widget of about dialogs, similar to what we
do for e.g. GtkAssistant.
|
|/ /
| |
| |
| | |
We have icon theme code to do that for us.
|
|\ \
| | |
| | |
| | |
| | | |
Avoid diagnostics for gcc-11 false positive out of bounds accesses
See merge request GNOME/gtk!3064
|
| | |
| | |
| | |
| | |
| | | |
This is a patch by Jeff Law <law@redhat.com> done in downstream Fedora
to fix the build with gcc 11.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
gl renderer: print fragment shader info
See merge request GNOME/gtk!3069
|
| | | |
| | | |
| | | |
| | | | |
It was logged twice the vertex shader info, instead
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | | |
Wip/jimmac/adjust for contemporary trends
Closes #3568 and #3560
See merge request GNOME/gtk!3060
|
| | | |
| | | |
| | | |
| | | |
| | | | |
- reflect button styling
- ignore backdrop for non buttons
|
| | | |
| | | |
| | | |
| | | |
| | | | |
- remove -alt specialcasing for a straight forward border like
everything else and avoid broken :dark and HC
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- tint borders dark on non default / blue / red buttons
- just use plain $borders_color otherwise
- fixes HC/HCi
- ditch -alt buttons
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- lighten up for contrast, less of an oldschool gradient
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/3568
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/3560
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- flat is the name of the game
- kids scream make it flat
- simplify mixins
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Remove guarantees we do not intend to hold
See merge request GNOME/gtk!3066
|
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | | |
The fact that we are using gdk-pixbuf for loading files currrently does not mean we will use it going forward.
Also, "anything gdk-pixbuf can load" does not mean anything, because what gdk-pixbuf can load is a compile-time option.
As new_from_resource() will assert() if it cannot load a resource, we must be very sure that people do not use anything but PNG and JPEG for resources and the docs were not clear on that.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Wayland: ignore touch/tablet events on destroyed surfaces [GTK4]
See merge request GNOME/gtk!3065
|
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When destroying a wl_surface (e.g. when a window or menu is closed), the
surface may continue to exist in the compositor slightly longer than on
the client side. In that case, the surface can still receive input
events, which need to be ignored gracefully.
In particular, this prevents segfaulting on wl_surface_get_user_data()
in that situation.
Reported in
https://gitlab.gnome.org/GNOME/gtk/-/issues/3296
The same issue for pointers/keyboards was reported in
https://bugzilla.gnome.org/show_bug.cgi?id=693338
and fixed with in
bfd7137ffbcbd8caa531d7a47d799fefb6605a5a
3625f17857328ae7e7aa43340f29efa56575a7b0
a8fc099a725543649fe3aab76943c14bdcd860fc
|
|\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | | |
Adwaita: less dramatic :active for undecorated buttons
Closes #3575
See merge request GNOME/gtk!3068
|
|/ / /
| | |
| | |
| | | |
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/3575
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
wayland: avoid set_cursor() when unchanged or invisible
Closes #3350
See merge request GNOME/gtk!3062
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In pointer_surface_update_scale(), only rescale the cursor surface when
the scale has actually changed and the cursor is on at least one output.
fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/3350
Right now, this issue is not completely understood, so it might also
involve some questionable handling of cursor surface by sway/wlroots.
However, irrespective of that issue, this patch avoids unnecessary calls to the
compositor, and there should be no drawback: Whenever the pointer enters
a new output, pointer_surface_update_scale() will be called again, such
that correct scaling of the cursor is still ensured.
There is a slight difference: When the cursor leaves the last output,
previously the image was reset to scale factor 1. Now, it keeps whatever
was last. That might be more sensible than the previous behaviour,
assuming that it's likely that when the cursor enter an output again, it
has the same scaling. Alternatively, if one cares about resource usage
at this level, it might make more sense to destroy the surface than
rescaling to 1.
|
|\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | | |
Fix surface and geometry computation for Windows (Win32)
Closes #3480
See merge request GNOME/gtk!3067
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Have an implementation of ->request_layout() and ->compute_size() for the Win32
surface backend so that we can properly display and move and resize the
windows, as we request from the Win32 APIs.
Hxndling Aerosnap properly is mostly done except for snap_up(), which needs to
to be looked at later.
|