| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
We were emitting a preedit-changed even if the preedit text did
not actually change, causing text views to scroll.
|
| |
|
|
|
|
|
|
|
|
| |
Adding the offset node broke serialization in 2 ways:
1. We store the enum value in the node, so make sure to not change it
for existing values
2. The offset node was missing in the deserialization lookup table
|
|
|
|
|
|
| |
Instead of fiddling around with scale in the iconhelper (and getting it
wrong), create a GtkScaler around the paintable that takes care of the
scaling.
|
|
|
|
| |
All users are gone. Use gtk_drag_set_icon_paintable() instead.
|
| |
|
| |
|
| |
|
|
|
|
| |
Patch is untested, because colorbuttons can't do DND at the moment.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This is intended for DND icons
|
|
|
|
|
|
|
| |
This is the equivalent snapshot function to pango_cairo_show_layout().
Not to be confused with gtk_snapshot_render_layout(), which is the
equivalent to gtk_render_layout().
|
|
|
|
| |
Push an offset node when append_node is called. That resets the offset.
|
|
|
|
|
|
|
|
|
| |
This is a special case of the transform node that does a 2D translation.
The implementation in the Vulkan and GL renderers is crude and just does
the same as the transform node.
Nothing uses that node yet.
|
| |
|
|
|
|
| |
Don't use Cairo when it's not needed.
|
|
|
|
| |
No need to use Cairo here.
|
|
|
|
| |
Don't create it using Cairo.
|
|\
| |
| |
| |
| | |
wayland: Don't paint if the window is unmapped
See merge request GNOME/gtk!32
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If a surface is unmapped by the client while gdk is processing updates,
(for example Firefox un-mapping its window on Expose events), the
windowing backend resources might be lost (for example with Wayland)
which can cause a crash in end_paint().
Make sure we drop the cairo surfaces as well when hiding the surface,
that will avoid the crash in gdk_surface_impl_wayland_end_paint() when
trying to attach the staging cairo surface to a released wl_surface,
these will be recreated when needed when the surface becomes visible
again and there is no need to keep such buffers around for a surface
which is not visible anyway.
https://bugzilla.gnome.org/show_bug.cgi?id=793062
|
| |
| |
| |
| |
| |
| |
| | |
When drawing onto a recording surface, source surfaces get cached.
But if we g_free() the surface data after we're done, that cache is
gonna point at invalid data...
|
| |
| |
| |
| |
| |
| |
| | |
If G_ENABLE_CONSISTENCY_CHECKS is defined (i.e. if our buildtype is
'debug'), add a opengl debug callback that prints all debug messages
with a severity higher than SEVERITY_NOTIFICATION as a warning to the
console.
|
| |
| |
| |
| | |
These will cause problems later on.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Turns out that GCC errors out when building the GLib test suite, as it
now checks for overflows in allocator functions, and we're testing for
those.
This would not be an issue for GTK, but since we're building GLib as a
subproject, we get failures for those as well.
Until we can find out how to disable errors for subprojects, or fix the
GLib test suite not to trip up warnings in GCC, we're going to live
without compiler warnings treated as errors for a while.
|
| |
| |
| | |
The option to enable fatal warnings in Meson is `--werror`.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Forcibly remove any ccache use, even if it's installed.
|
| | |
|
| |
| |
| |
| |
| | |
Now that there's no longer a need to keep the renderer around for Cairo
rendering, don't do that then.
|
| |
| |
| |
| | |
It's not needed to create Cairo nodes anymore.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This way, we can postpone the actual rendeing of the node until the
renderer. This allows the renderer to choose the right scale to
render at, so it can decide to use 2x scale for hidpi on its own.
Last but not least, it makes all nodes independent of the context they
are created in, because they do not need to know at snapshot time what
they will ultimately be rendered into.
|
| |
| |
| |
| |
| | |
This is in preparation for the next commits which switch Cairo nodes to
recording surfaces.
|
|\ \
| | |
| | |
| | |
| | | |
bug 773299 2nd
See merge request GNOME/gtk!79
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Set the display for each event that we put.
Also reorganize the dnd_event_put() function a bit, giving it a surface
directly instead of setting it by implication.
https://bugzilla.gnome.org/show_bug.cgi?id=773299
|
|\ \ \
| |/ /
| | |
| | |
| | | |
bug 773299
See merge request GNOME/gtk!78
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
dest_surface is going to always be NULL for source contexts.
Previously we used to put the root window there to pass this check,
but root windows are gone (and root surfaces never existed to begin
with), so we have to adapt.
https://bugzilla.gnome.org/show_bug.cgi?id=773299
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This affects gdk_device_query_state() for the virtual device. It has
no window, and is forced to query the display itself, and display
defaults its scale to 1 even for HiDPI desktops. Use the same
"query scale of a NULL monitor" trick that we use in other places
to get the global desktop scale.
https://bugzilla.gnome.org/show_bug.cgi?id=773299
|
|/ /
| |
| |
| | |
https://bugzilla.gnome.org/show_bug.cgi?id=773299
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
https://gitlab.gnome.org/GNOME/gtk/merge_requests/66 introduced spurious
red/green fore/background.
Also, the GtkVideo stuff didn't get regenerated in.
|
|\ \
| | |
| | |
| | |
| | | |
theme: Be more selective when adding margins to toolbar items
See merge request GNOME/gtk!66
|
| | |
| | |
| | |
| | |
| | | |
Only add margins to direct children of toolbar items, this fixes the
gaps between linked buttons inside custom toolbar items.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
... and all the implementations.
Input shapes still exist.
|