| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
This attempts to fix the counter-intuitive resizing of surfaces in GTK4 where
the surface grows or shrinks at the right and/or bottom edge when the window
resized from the top and/or left edge(s).
This is not yet perfect as the window stutters upon resizing from the top
and/or left edges, but at least makes resizing more intuitive.
|
|
|
|
|
|
| |
Remove the 'resized' member from the GdkWin32Surface structure, as we already
have a structure with a member that keeps track of whether a surface is being
resized, so we can just use that and avoid some confusion in the process
|
|\
| |
| |
| |
| | |
Merge branch 'revert-82ab039a' into 'master'
See merge request GNOME/gtk!3196
|
|/
|
|
|
|
|
|
|
|
|
| |
Revert "Merge branch 'disable-macos-ci' into 'master'"
See merge request GNOME/gtk!3192
(cherry picked from commit 6601d79b2deb4388cbf19d2ab24fa0c9dd033382)
0ce0402e Revert "Merge branch 'disable-macos-ci' into 'master'"
b1c1e02c ci: Add debug spew on macos
5ff843f9 Stop passing introspection=false to graphene
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Icon fixup
See merge request GNOME/gtk!3178
|
| |
| |
| |
| | |
We have an app icon, lets use it.
|
|/
|
|
| |
We are no longer a nightly print editor.
|
|
|
|
| |
We're now a respectable, stable node editor.
|
| |
|
|\
| |
| |
| |
| | |
4.0 backports
See merge request GNOME/gtk!3168
|
| |
| |
| |
| |
| | |
This one includes mesa-libGLES-devel, needed to make
the gstreamer module build.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Whenever we communicate targets, we need to the union, otherwise
we don't tell the other side about our serialization. This makes
drops of images from gtk4-icon-browser to gimp and libreoffice
succeed in transferring data.
Fixes: #3654
|
| |
| |
| |
| |
| |
| |
| |
| | |
When creating the output stream for a drop, we must
pass the mimetypes we support, otherwise the picking
of the right handler does not work.
Fixes: #3652
|
| |
| |
| |
| |
| | |
We ref the content formats here, so we better unref it
when done.
|
| |
| |
| |
| | |
Fix some glaring misindentation.
|
| |
| |
| |
| |
| |
| |
| |
| | |
GModule requires the .so file extension on macOS for historic reasons.
However Meson defaults to .dylib for modules, so we need to override
it to get the correct extension.
Fixes #3645.
|
| |
| |
| |
| |
| |
| | |
We need to drag a texture, not a paintable.
Fixes: #3648
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
As was pointed out in #3646, some of the content here
was a bit outdated.
Fixes: #3646
|
| |
| |
| |
| |
| |
| | |
We never get here. The compiler says so.
Pointed out in https://www.viva64.com/en/b/0793/
|
| |
| |
| |
| |
| |
| | |
We never get here. The compiler says so.
Pointed out in https://www.viva64.com/en/b/0793/
|
| |
| |
| |
| |
| |
| | |
Don't use the index before we've checked its good.
Pointed out in https://www.viva64.com/en/b/0793/
|
| |
| |
| |
| |
| |
| | |
We already know desktop_notification_id is not NULL.
Pointed out in https://www.viva64.com/en/b/0793/
|
| |
| |
| |
| |
| |
| | |
We don't need to set these fields more than once.
Pointed out in https://www.viva64.com/en/b/0793/
|
| |
| |
| |
| |
| |
| |
| | |
translate_keysym was expecting its arguments the
other way around.
Pointed out in https://www.viva64.com/en/b/0793/
|
| |
| |
| |
| |
| |
| |
| | |
The post_insert_fixup helper function was confused about
its argument order.
Pointed out in https://www.viva64.com/en/b/0793/
|
| |
| |
| |
| |
| |
| | |
We only need to set EXPLICIT_NOTIFY once.
Pointed out in https://www.viva64.com/en/b/0793/
|
| |
| |
| |
| |
| |
| |
| | |
This function was not resetting computed as it meant
to because the last loop was never executed.
Pointed out in https://www.viva64.com/en/b/0793/
|
| |
| |
| |
| |
| |
| |
| | |
This code did not make sense; it was incrementing
the wrong variable.
Pointed out in https://www.viva64.com/en/b/0793/
|
| |
| |
| |
| | |
We don't support this filter, currently.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This function was not doing the right thing.
Once we are doing the right thing and not compare
shadows as unequal, some reftests that inhibit
snapshots for a few frames now hang forever, since
we are no more redrawing unnecessarily. Fix that
with an explicit queue_draw.
|
| |
| |
| |
| | |
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/3643
|
| |
| |
| |
| |
| |
| |
| | |
This code is very similar to the handling for these
targets in the clipboard case.
Fixes: #3642
|
| |
| |
| |
| |
| | |
The code handles it just fine. The length check was
an erronous addition.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Sometimes the size will exceed the minimum bounds. For example crazy
applications like the widget factory that contains the world, or when a
user interactively resizes a window to be larger than the monitor the
window is on is.
The former is questionable, but the latter is not, and from here we
can't really see the difference, so just stop complaining.
Closes: https://gitlab.gnome.org/GNOME/gtk/-/issues/3035
|
| |
| |
| |
| |
| | |
The example series only has 9 steps now. Remove remnants
of step 10.
|
| |
| |
| |
| |
| | |
Emphasize that native dialogs aren't widgets, and are not
kept alive by GTK.
|
| |
| |
| |
| | |
It is too flaky to be useful.
|
| |
| |
| |
| |
| | |
We need to synchronize when moving the texture between contexts, or we
get glitches with VA-API decoding.
|
| |
| |
| |
| | |
There's really no point in running them.
|
| |
| |
| |
| | |
This way we can get syntax highlighting.
|
| |
| |
| |
| |
| | |
Otherwise tools processing the description of GtkWidget will be *very*
confused.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Otherwise the nice markdown tables don't line up.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds a "release" destructor for the gtk_surface1 interface which
signals to the server that a surface has been destroyed on the client
side, which the current "destroy" does not do.
Ideally the protocol would have specified a destroy request marked as
destructor to handle this automatically, however this is no longer
possible due to the destroy method being implicitly generated in the
absence of an explicit request in the protocol. Adding a destroy request
marked as destructor now would generate a new destroy method that
unconditionally would send the request to the server, which would break
clients running on servers not supporting that request.
|
| |
| |
| |
| |
| | |
These files have not been kept up to date, and
glade doesn't work with GTK4 currently.
|