| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- 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.
|
| | |
| | |
| | |
| | | |
This improves consistency for the code.
|
| | |
| | |
| | |
| | | |
gdk_win32_toplevel_present() should now be returning nothing, not a gboolean.
|
|/ /
| |
| |
| |
| |
| | |
In line with what is done with the Wayland backend, enable the mapped state
independently as needed from the toplevel surface presentation, and also enable
the mapped state if necessary when presenting the popup surface.
|
| | |
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
| |
Add an option to disable css rebuilds. This allows
to build GTK from release tarballs (Which are including
the css) without a sassc dependency.
|
|\
| |
| |
| |
| |
| |
| | |
Matthiasc/for master
Closes #3565
See merge request GNOME/gtk!3061
|
| |
| |
| |
| | |
Fixes #3565, among other things.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Visual Studio 2013 is just shy of being sufficiently C99-compliant to
build GTK master, as it did not support snprintf() in its CRT
implementation.
Use g_snprintf() to cover for this.
|
| |
| |
| |
| |
| | |
Some compilers somehow do not have `inline` defined, so include glib.h
to ensure that keyword is defined.`
|
|/
|
|
| |
Seems that msvc does not like that.
|
|\
| |
| |
| |
| | |
Clean ups in seat default
See merge request GNOME/gtk!3057
|
| | |
|
|/ |
|
|\
| |
| |
| |
| | |
gdkdevice: use g_set_object to set the associated device
See merge request GNOME/gtk!3049
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
Add critical if widget has a parent during dispose
See merge request GNOME/gtk!3053
|
| | |
| | |
| | |
| | |
| | |
| | | |
This is a refcounting bug. Be very verbose about it instead of trying to
call a function that releases a reference to the widget without
references.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Remove incorrect unparenting guidance from migration guide
See merge request GNOME/gtk!3050
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
This rule is almost always wrong, and we're having some trouble agreeing
on replacement text. Let's remove the whole paragraph for now, to avoid
confusion.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Improve GtkBuilder documentation
See merge request GNOME/gtk!3055
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In GTK 3, it was pretty much always better to use
gtk_builder_new_from_whatever() rather than
gtk_builder_add_from_whatever(). But in GTK 4, this is no longer
generally true. Let's add some context on when you want to use one or
the other.
|
| |/ /
| | |
| | |
| | | |
Thanks to Benjamin for helping with the language.
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
Expand event controller API changes section of GTK 4 porting guide
See merge request GNOME/gtk!3054
|
| |/
| |
| |
| | |
There is more to say about changes to GtkEventController.
|
|\ \
| |/
|/|
| |
| | |
ci: Specify `only` for other jobs
See merge request GNOME/gtk!3052
|
| |
| |
| |
| | |
Don't run CI on macOS for forks.
|
|/
|
|
| |
Otherwise MRs will only run macOS jobs.
|
|\
| |
| |
| |
| |
| |
| | |
Adwaita: fine tune flat button styling
Closes #3481
See merge request GNOME/gtk!3046
|
| |
| |
| |
| |
| |
| |
| | |
- enough contrast for hover and active, while noticably different in
normal nad headerbar context (and both light and dark variants).
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/3481
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
HC: switch border color
Closes #3460
See merge request GNOME/gtk!3048
|