| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
Now that we have gtk_drag_check_threshold_double(), be consistent with
other draggable widgets and make sure we don't take over a drag before a
child does.
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/3513
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If multiple nested widgets have drag sources on them, both using bubble
phase, we need to reliably pick the inner one. Both of them will try to
start dragging, and we need to make sure there are no situations where the
outer widget starts drag earlier and cancels the inner one.
Currently, this can easily happen via integer rounding: start and current
coordinates passed into gtk_drag_check_threshold() are initially doubles
(other than in GtkNotebook and GtkIconView), and are casted to ints. Then
those rounded values are used to calculate deltas to compare to the drag
threshold, losing quite a lot of precision along the way, and often
resulting in the outer widget getting larger deltas.
To avoid it, just don't round it. Introduce a variant of the function that
operates on doubles: gtk_drag_check_threshold_double() and use it instead
of the original everywhere.
|
| |
|
|
| |
It was passing offsets as current oordinates.
|
| |
|
|
|
|
|
|
|
| |
This was needed to work around widgets claiming event sequences on press,
by ignoring them and starting the drag anyway unless they have certain
event controllers on them.
The most visible offender was GtkButton, but since the last commit it
doesn't claim the sequence anymore and we can remove the hack.
|
| |
|
|
| |
Make it possible to drag windows from check buttons in future.
|
| |
|
|
|
|
|
|
| |
Currently GtkButton claims the sequence both on press and on release. Stop
claiming it on press and only do it on release, allowing drags to start
from it.
This will allow to remove a hack from GtkWindowHandle.
|
| |\
| |
| |
| |
| | |
Tell pango not to round glyph positions
See merge request GNOME/gtk!2058
|
| | |
| |
| |
| |
| | |
When looking for ascii glyphs, we must match
the pango shape flags that GTK is using.
|
| | |
| |
| |
| |
| |
| |
| | |
Before turning off pangos rounding of glyph positions,
we must check if the cairo we are using is new enough
to have working subpixel positioning (the relevant
cairo commit is 52a7c79fd4ff96bb5fac175f0199819b0f8c18fc).
|
| | |
| |
| |
| |
| | |
With subpixel positioning, we need to offset the
cached glyphs by their phase.
|
| |/
|
|
| |
(cherry picked from commit 5a5bb9099e8e8781a307ce3f9f72e52937d3d411)
|
| |\
| |
| |
| |
| | |
Matthiasc/for master
See merge request GNOME/gtk!3127
|
| | | |
|
| | |
| |
| |
| |
| | |
These files have not been kept up to date, and
glade doesn't work with GTK4 currently.
|
| | |
| |
| |
| | |
Put these images into gtk/icons, where they belong.
|
| | |
| |
| |
| | |
The inspector no longer sets a window icon.
|
| | |
| |
| |
| |
| |
| | |
Remove some unnecessary uses of GtkStyleContext where
we can directly go to the GtkCssStyle, and and drop
unnnecessary includes.
|
| | |
| |
| |
| |
| | |
Avoid using GtkStyleContext unnecessarily, just go
to the css node directly.
|
| | |
| |
| |
| |
| |
| | |
Move the tools directory to be toplevel, and instead of
recompiling sources twice, link them with the our new
static libgtk.a.
|
| |\ \
| |/
|/|
| |
| | |
gskglshaderbuilder: bind correct uv location
See merge request GNOME/gtk!3128
|
| |/ |
|
| |\
| |
| |
| |
| | |
builder-tool: Translate GtkImage:pixbuf
See merge request GNOME/gtk!3126
|
| | |
| |
| |
| |
| |
| | |
The pixbuf property doesn't exist anymore. It is
commonly set to a path in ui files, so translate it
to the file property.
|
| |\ \
| | |
| | |
| | |
| | | |
OpenGL gradient rendering improvements and additions
See merge request GNOME/gtk!3105
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| | |/
| |/|
| | |
| | | |
docs: Add gtk_widget_grab_default to migration guide
See merge request GNOME/gtk!3125
|
| |/ /
| |
| |
| | |
Point out the replacement for this api.
|
| |\ \
| |/
|/|
| |
| | |
widget: get_name() is not nullable
See merge request GNOME/gtk!3124
|
| |/
|
| |
Partial revert of !2905
|
| |\
| |
| |
| |
| |
| |
| | |
widget: Fix can-focus
Closes #3610
See merge request GNOME/gtk!3123
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Setting can-focus to FALSE on a widget is supposed
to prevent focus from entering the entire subtree.
So when we grab focus directly to a widget, we need
to check the can-focus flag not just of the widget
itself, but all its ancestors.
Fixes: #3610
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Search entry capture
Closes #3098
See merge request GNOME/gtk!3115
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is an unfortunate naming clash, but it avoids
an event handling clash between the capture widget
and its children.
Fixes: #3098
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is an unfortunate naming clash, but it avoids
an event handling clash between the capture widget
and its children.
Fixes: #3098
|
| | | |
| | |
| | |
| | |
| | | |
The css section was inserted between the example
and the sentence referring to it.
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
Css crossfade color
See merge request GNOME/gtk!3122
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
The CSS Image Spec (Level 4) allows colors in
cross-fade expressions to specify solid-color images.
Support this.
|
| | | |
| | |
| | |
| | | |
Add a way to create a solid color image.
|
| |/ /
| |
| |
| | |
Tweak the css docs slightly.
|
| |\ \
| | |
| | |
| | |
| | | |
Minor fixes to gtkgstsink
See merge request GNOME/gtk!3120
|
| | | |
| | |
| | |
| | |
| | |
| | | |
The video frame needs to stay mapped while the texture is in use.
Avoid using g_memdup because the structure is not supposed to be moved.
|
| | | |
| | |
| | |
| | | |
We can do that so we should.
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
css: Fix text-decoration-line support
Closes #3621
See merge request GNOME/gtk!3121
|
