| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
They are not used anymore.
Gone with them are PropertyNotify events.
|
| |
|
|
|
|
|
| |
... and just unset it from GtkWindow instead of fiddling with
properties.
|
|
|
|
|
|
| |
And with it, remove the selections section from the docs.
So selections are gone for good now.
|
|
|
|
|
| |
All callers in gtk seem to be ok with it, and it makes sense if
we are dealing with events as "static after delivered".
|
|
|
|
| |
Those places can do with an extra reference.
|
| |
|
|
|
|
|
|
|
| |
There is a gtk_event_controller_scroll_set_flags() call that's meant
to be called after construction (eg. due to scrolledwindow relayouts
hiding/showing scrollbars). The property shouldn't be construct-only
for consistence.
|
| |
|
|
|
|
|
| |
Using stack allocated GdkEvent will not be ok when they become
objects.
|
|
|
|
|
|
| |
Now all events structs are private, it doesn't make as much sense
having GdkEventPrivate wrapping allocating events. This is a first
step towards removing it.
|
|
|
|
|
|
| |
It won't stand true anymore that the GdkEventType argument is the
first field of the GdkEvent* structs. All callers have been updated
to use event->any.type instead.
|
|
|
|
|
| |
Make all specific event structs contain a GdkEventAny, so the base
struct can be extended without modifying structs all over the place.
|
|
|
|
| |
Let the gesture itself handle the events.
|
|
|
|
| |
It's not used anymore.
|
|
|
|
| |
This is Xdnd-specific and doesn't need to happen elsewhere.
|
|
|
|
|
| |
With this, the GDK_EVENT_SELECTION_REQUEST and GDK_EVENT_SELECTION_CLEAR
and the associated GtkWidget signals are gone, too.
|
| |
|
|
|
|
|
|
|
| |
It's not needed anymore, now that we can look at the content provider's
formats.
Alose remove all the API in GTK that was used to set it.
|
|
|
|
|
| |
Instead of claiming the selection in GTK, claim it in the X11 dnd code.
Also handle SelectionRequest and SelectionClear X events there.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of just passing the GdkContentFormats, we are now passing the
GdkContentProvider to gdk_drag_begin().
This means that GDK itself can now query the data from the provider
directly instead of having to send selection events.
Use this to provide the private API gdk_drag_context_write() that allows
backends to pass an output stream that this data will be written to.
Implement this as the mechanism for providing drag data on Wayland.
And to make this all work, implement a content provider named
GtkDragContent that is implemented by reverting to the old DND
drag-data-get machinery inside GTK, so for widgets everything works just
like before.
|
|
|
|
|
| |
These changes belong to the scale button autoscrollling
commit.
|
|
|
|
| |
We can reuse the button gesture here.
|
|
|
|
|
| |
Use the smooth autoscrolling that the scale can do,
and at the same time stop using legacy event signals.
|
|
|
|
|
|
| |
Attaching another gesture from the outside does not
work currently, so let widgets share their button's
gesture for now.
|
|
|
|
| |
This will be used to scroll the scale in scale buttons.
|
|
|
|
|
|
|
|
| |
Scrolling a path bar is of marginal usefulness - you need to
find a really deep place in your filesystem hierarchy in order
to scroll one or two places at best. And the code we had for
this was not working. And it was using legacy event handlers.
Instead of fixing it, remove it.
|
|
|
|
|
|
| |
This code was doing horrible things, and the atk documentation
for the focus tracking feature says that this is deprecated and
not used anymore. So lets not do it.
|
|
|
|
| |
This does not cost us much, and improves consistency.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Mark the following signals as deprecated:
event, event-after, button-press-event, button-release-event,
touch-event, scroll-event, motion-notify-event, enter-notify-event,
leave-notify-event, property-notify-event, selection-clear-event,
selection-request-event, selection-notify-event, selection-received,
selection-get, proximity-in-event, proximity-out-event. Most
of these have suitable replacements in event controllers and
gestures already. The selection-related signals will soon be
irrelevant when selection handling moves to GDK.
Set G_ENABLE_DIAGNOSTIC=1 to see deprecation
warnings for uses of these signals.
|
|
|
|
|
| |
Public headers need to be listed in gtk/meson.build.
This was overlooked when I added the controller.
|
|
|
|
|
| |
We can use the new motion event controller that
was introduced for this purpose.
|
|
|
|
| |
We can just use a multipress gesture for this purpose.
|
|
|
|
| |
We can use the new motion event controller for this.
|
|
|
|
| |
This lets us avoid legacy event signals here.
|
|
|
|
|
| |
This can serve as a replacement for the legacy
event signals for enter/leave/motion notify.
|
| |
|
|
|
|
|
| |
You don't start a dnd operation with a device, you start it with an
event.
|
|
|
|
| |
Nobody ever does that and special cases are evil.
|
|
|
|
| |
It was unused.
|
|
|
|
| |
Replace the motion_notify handler by a drag gesture.
|
|
|
|
|
|
| |
This makes drag icons set from icon names come out
at a size that it large enough to not disappear under
the drag cursor.
|
|
|
|
|
|
| |
This lets us use the new icon-size machinery to
ensure we don't have tiny drag icons when using
named icons.
|
|
|
|
|
|
|
| |
Instead, pass the actions as part of gdk_drag_begin() and insist DND is
always managed.
A new side effect is that gdk_drag_begin() can now return %NULL.
|
|
|
|
| |
We only use the pointer.
|
|
|
|
|
| |
This way, we don't need root coordinates when computing the dnd start
position.
|
|
|
|
|
| |
There's no need to call it from GTK anymore, because we pass the device
to gdk_drag_begin().
|
|
|
|
| |
At least wait until we've received the previous one.
|
|
|
|
|
| |
There's only one that's ever used, so delete the others and rename this
one to gdk_drag_begin().
|
|
|
|
| |
It is a bit odd to drag nothing around, so set an icon.
|