| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
| |
- make sure both non active and active states are contrasty
https://bugzilla.gnome.org/show_bug.cgi?id=763802
|
|
|
|
|
|
| |
- selected bg was set lighter without appropriate fg color
https://bugzilla.gnome.org/show_bug.cgi?id=763804
|
|
|
|
|
|
| |
- make the trough more visible for HCI
https://bugzilla.gnome.org/show_bug.cgi?id=763805
|
| |
|
| |
|
|
|
|
| |
... since it ends up jumpy.
|
|
|
|
| |
adds some padding to the "connect to server" label
|
|
|
|
|
| |
adresses the style part of
https://bugzilla.gnome.org/show_bug.cgi?id=764118
|
| |
|
|
|
|
|
|
| |
Fix an oversight that should have happened in the gadget refactoring:
An active switch should be :checked, just like togglebuttons,
checkbuttons, etc.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gtk+ currently depends on the scaling factor and the cairo device scale
of both the backend surfaces and image surfaces to be equal.
Until now we didn't apply a cairo device scale at all and depended on the
automatic scaling of CGContexts. This works when drawing with cairo but
fails in case of image surfaces, which get requested at a too small size.
To make the quartz backend behave more like the X11 one, set the cairo device
scale on the surface in gdk_quartz_ref_cairo_surface(). As this conflicts
with the default scaling done by CGContext (we would get double scaling)
undo the CGContext scaling using CGContextScaleCTM().
This patch is based on the following patches by Brion Vibber:
https://bugzilla.gnome.org/show_bug.cgi?id=740199#c4
https://bugs.freedesktop.org/show_bug.cgi?id=69796#c4
https://bugzilla.gnome.org/show_bug.cgi?id=763779
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
I've made this change for installed tests a while ago. It doesn't
make sense for distcheck to do it differently.
|
|
|
|
| |
This matches what GTK+ does now.
|
|
|
|
| |
Not sure when this went missing, just fix the formatting.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
When loading a per-theme settings.ini file, look for it in
the same directory where we found the gtk.css file for the
theme. Previously, we were always looking in
$prefix/share/themes/THEME/gtk-3.0/, even if the css was
loaded from somewhere else.
https://bugzilla.gnome.org/show_bug.cgi?id=641354
|
|
|
|
|
|
|
|
|
|
| |
With this change, we now look in
$XDG_DATA_HOME/themes/THEME/gtk-3.x
$HOME/.themes/THEME/gtk-3.x
$XDG_DATA_DIRS/themes/THEME/gtk-3.x
GTK_DATA_PREFIX/themes/THEME/gtk-3.x
https://bugzilla.gnome.org/show_bug.cgi?id=641354
|
|
|
|
|
|
|
|
|
| |
If the configure-event gives us the same size as we had before,
which is common for animation resizes, then try to keep the
existing buffer around. This saves us a memfd_create() syscall
on every frame.
https://bugzilla.gnome.org/show_bug.cgi?id=763350
|
| |
|
| |
|
|
|
|
|
|
| |
Add squiggly underlines and background, and make the markup editable.
https://bugzilla.gnome.org/show_bug.cgi?id=763741
|
|
|
|
|
|
|
| |
This way, we can ensure that we queue redraws on the full ink rect. This
is particularly visible for squiggly underlines in spell checking.
https://bugzilla.gnome.org/show_bug.cgi?id=763741
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Now that GdkWaylandDeviceData is gone, the functions prefixed
"gdk_wayland_device_" and taking a GdkWaylandSeat as first
parameter feel out of place. Renaming those makes it more obvious
that it's seat functions.
https://bugzilla.gnome.org/show_bug.cgi?id=763859
|
|
|
|
|
|
| |
It's no longer used.
https://bugzilla.gnome.org/show_bug.cgi?id=763859
|
|
|
|
|
|
|
| |
And use GdkWaylandSeat in all of those. The variable names have also
been updated.
https://bugzilla.gnome.org/show_bug.cgi?id=763859
|
|
|
|
|
|
|
|
| |
It's the same than gdk_device_get_seat() nowadays. Also, rename the
usages of GdkWaylandDeviceData to GdkWaylandSeat in the functions
affected by the removal.
https://bugzilla.gnome.org/show_bug.cgi?id=763859
|
| |
|
|
|
|
|
|
|
| |
Add the image-button style class to this button (this doesn't
work automatically here, since this is a toggle button).
https://bugzilla.gnome.org/show_bug.cgi?id=763604
|
|
|
|
|
|
|
| |
This reinstates the between-the-rows highlight that was lost
at some point.
https://bugzilla.gnome.org/show_bug.cgi?id=763808
|
|
|
|
|
|
|
|
| |
Stop using the .dnd style class, and instead use the
:drop(active) pseudo state, together with .before and .after
classes.
https://bugzilla.gnome.org/show_bug.cgi?id=763808
|
|
|
|
|
|
| |
Copy changes to drag highlight drawing from gtkdnd.c to gtkdnd-quartz.c.
https://bugzilla.gnome.org/show_bug.cgi?id=763808
|
|
|
|
|
|
|
|
|
|
|
|
| |
When animating, we might be changing the size allocation of the previous
stack child. However, we were not querying the size in the process
meaning you would often see warnings about allocating the size without
knowing what it should be.
This simply adds an innocuous size request, since responding to last_child
sizing requests is not all that critical in the transition.
https://bugzilla.gnome.org/show_bug.cgi?id=763900
|
|
|
|
|
|
|
|
| |
Instead of hardcoding the size of the widgets. This makes the output
closer to real widgets and fixes the blurry icons. I've also added a
scale.
https://bugzilla.gnome.org/show_bug.cgi?id=763758
|
|
|
|
|
|
|
|
|
| |
We were just relying on the drag context finalize() to destroy
the window. But with garbage-collected bindings, that might
not happen as soon as we like, so explicitly hide the window
when the drag ends successfully.
https://bugzilla.gnome.org/show_bug.cgi?id=763659
|
|
|
|
|
|
|
|
|
|
|
| |
This isn't an issue at the moment. Only exporting to a file can fail
by setting by setting an error and it happens to correctly return
GTK_PRINT_OPERATION_RESULT_ERROR regardless of this code.
Still, let's make this block of code more correct to prevent future
changes from introducing broken behaviour.
https://bugzilla.gnome.org/show_bug.cgi?id=763731
|
| |
|
| |
|
| |
|
| |
|