| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Eventually, most of these tests should be dropped.
|
| |
|
|
|
|
| |
These are all on GtkBox or enumerating children.
|
|
|
|
|
| |
Replace all uses of gtk_container_add on windows
by gtk_window_set_child.
|
|
|
|
|
|
| |
And fix all the errors and warnings resulting from that
See #2491
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a huge reorganization of GtkDropTarget. I did not know how to
split this up, so it's unfortunately all one commit.
Highlights:
- Split GtkDropTarget into GtkDropTarget and GtkDropTargetAsync
GtkDropTarget is the simple one that only works with GTypes and offers
a synchronous interface.
GtkDropTargetAsync retains the full old functionality and allows
handling mime types.
- Drop events are handled differently
Instead of picking a single drop target and sending all DND events to
it, every event is sent to every drop target. The first one to handle
the event gets to call gdk_drop_status(), further handlers do not
interact with the GdkDrop.
Of course, for the ultimate GDK_DROP_STARTING event, only the first
one to accept the drop gets to handle it.
This allows stacking DND event controllers that aren't necessarily
interested in handling the event or that might decide later to drop
it.
- Port all widgets to either of those
Both have a somewhat changed API due to the new event handling.
For the ones who should use the sync version, lots of cleanup was
involved to operate on a sync API.
|
| |
|
|
|
|
| |
Saves tons of code.
|
| |
|
|
|
|
| |
Replace these calls with direct use of GMainContext api.
|
| |
|
|
|
|
|
|
| |
Now that drop targets are event controllers,
we can just use gtk_event_controller_get_widget.
Update all callers.
|
|
|
|
|
|
| |
Since drop targets are now just event controller,
gtk_widget_add/remove_controller works just fine
for them.
|
|
|
|
|
|
| |
These no longer have any effect.
Update all callers.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This is in preparation of using input streams to show that these
coordinates aren't needed most of the time and can otherwise be saved
during GtkWidget::drag-drop.
|
|
|
|
| |
It's now called GdkContentsFormat
|
|
|
|
|
|
|
| |
warning: We don't do any same-app checks anymore so you currently can
copy local data into external apps.
This will be fixed later.
|
|
|
|
|
|
|
|
|
| |
Instead of allowing people to pass a uint user-data, insist on them
comparing mime types.
The user data was a uint instead of a pointer anyway, so uniqueness
could not be guaranteed and it caused more issues than it was worth.
And that's ignoring the fact that it basically wasn't used.
|
|
|
|
|
| |
This gets rid of GtkTargetEntry in the API and consistently uses
GtkTargetList.
|
| |
|
|
|
|
| |
Adapt all our tests and examples to the new initialization api.
|
|
This shows a minimal setup for enabling non-row DND from a treeview.
|