| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Document that we support TIFF as well.
|
|
|
|
|
| |
Clang things that timings can be NULL here,
and I think it might be right.
|
|
|
|
|
| |
Clang things that timings can be NULL here,
and I think it might be right.
|
|
|
|
|
|
|
| |
Clang was complaining that we never use the
value stored in mime_type. Just don't store it,
we are only interested in the side-effect
(interning the string).
|
| |
|
| |
|
|
|
|
| |
Make short string tokens static.
|
|
|
|
|
|
|
| |
The documentation already tells you not to
use this function.
Ifdef the remaining users in the X11 backend.
|
|\
| |
| |
| |
| | |
macos: Drag and drop should not freeze applications
See merge request GNOME/gtk!5291
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
A Drag surface does not have a parent surface. Therefore, if we initialize
it with one, it's inheriting the frame clock from the parent, but the
drag surface is not linked to the parent. Once the drag surface is destroyed,
it's disposing the frame clock, which results in a "frozen" application.
|
| |
| |
| |
| |
| |
| | |
This is an extra safeguard that avoids grabbing resources longer than
nessecary. It also ensures the resource is removed from the drag,
so it is not freed again.
|
| |
| |
| |
| |
| | |
New code (macOS 10+ should support the NSDraggingSource protocol:
https://developer.apple.com/documentation/appkit/nsdraggingsource.
|
| |
| |
| |
| | |
Update the docs for gdk_display_get_monitor_at_surface.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
gdkdisplay: Document get_monitor_at_surface can return NULL
Closes #5075
See merge request GNOME/gtk!4917
|
| | |
| | |
| | |
| | | |
Fixes https://gitlab.gnome.org/GNOME/gtk/-/issues/5075
|
| | | |
|
| | |
| | |
| | |
| | | |
It is empty now.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Detangle compute_size, among other things.
|
| | |
| | |
| | |
| | |
| | | |
Like the GdkWaylandToplevel split-off, this needs some
more cleanup.
|
| | |
| | |
| | |
| | | |
This still needs some more cleanup.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Split gdkwaylandsurface.h into itself,
gdkwaylandtoplevel.h and gdkwaylandpopup.h.
This is in preparation for splitting the
types for real.
|
| | |
| | |
| | |
| | |
| | | |
Move these to GdkWaylandToplevel and GdkWaylandPopup
as appropriate.
|
| | |
| | |
| | |
| | | |
This is where it belongs.
|
| | |
| | |
| | |
| | | |
Another toplevel-only thing.
|
| | |
| | |
| | |
| | | |
This is popup-only functionality.
|
| | |
| | |
| | |
| | | |
This is only used for popups, so move it there.
|
| | |
| | |
| | |
| | | |
Another toplevel-only feature.
|
| | |
| | |
| | |
| | | |
Another toplevel-only thing.
|
| | |
| | |
| | |
| | | |
Another toplevel-only thing.
|
| | |
| | |
| | |
| | | |
This is a toplevel property.
|
| | | |
|
| | |
| | |
| | |
| | | |
It is only used in one place.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
gdk/wayland: set requesting surface to xdg-activation
See merge request GNOME/gtk!5293
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The argument to xdg_activation_token_v1_set_surface is documented to be the
surface requesting the activation, not the surface to be activated, which is
given later when calling xdg_activation_v1_activate.
(c.f. https://gitlab.freedesktop.org/wayland/wayland-protocols/-/commit/36cee4bdbcaf3a75f567315809953b5e21d703da)
Use the same logic as in gdk_wayland_app_launch_context_get_startup_notify_id,
i.e. if we have a surface with focus, set that, otherwise set NULL.
This fixes requesting urgent/focus on wlroots (compositors like Sway, etc.),
which was blocked as the surface requesting the activation didn't have focus.
Signed-off-by: Joan Bruguera <joanbrugueram@gmail.com>
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Make it safe to call gdk_x11_app_launch_context_get_startup_notify_id
with a NULL info.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We have various layers where we store the startup ID for a request,
since this API does not have a GdkToplevel that we can refer about
for the Wayland platform, this is the most obvious candidate to
start untangling these various layers.
Deprecate this call, it is already unused in the gtk/ side.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In the way towards deprecating gdk_display_notify_startup_complete(),
make gdk_toplevel_set_startup_id() on X11 perform this piece of messaging
itself. It should be harmless that the message is emitted twice, if
callers do still use that API.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This call has everything to perform activation as specified by the
xdg_activation protocol, notably a surface to activate as opposed to
gdk_display_notify_startup_complete().
Make activation happen here, so that the surface gets activated when
its gets a startup ID assigned.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The owner_events=TRUE grab makes GDK on X11 see events happening
outside every client window as received on the grab window.
Additionally check that the pointer is inside the grab window
(i.e. it received GDK_CROSSING_NORMAL crossing events for the
core pointer) in order to handle clicks happening outside client
windows.
These new paths are expected to be a no-op on Wayland, and to
also work for touchscreen input on X11, due to emulated pointer
events.
|
| | | |
| | | |
| | | |
| | | | |
Handle the case of clipboard text with CR line endings
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The function was added to glib in 2.75.1. This fixes gtk's build with
the glib main branch.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Allows us to make use of this API without depending
on bleeding-edge glib
|
| | | |
| | | |
| | | |
| | | | |
Fixes: #5441
|