summaryrefslogtreecommitdiff
path: root/gtk/gtkgesturedrag.c
Commit message (Collapse)AuthorAgeFilesLines
* events: reorganize gettersMatthias Clasen2020-02-211-1/+1
| | | | | | | | | | Restructure the getters for event fields to be more targeted at particular event types. Update all callers, and replace all direct event struct access with getters. As a side-effect, this drops some unused getters.
* Strip const from GdkEventMatthias Clasen2020-02-211-1/+1
| | | | | Events are refcounted structs, and we generally don't pass these as const.
* gtk: fix all uses of g_cclosure_marshal_genericChristian Hergert2019-06-021-3/+16
| | | | | | | | | | | | | | This adds specific marshallers for all of the locations where a generic marshaller is being used. It also provides va_marshallers to reduce the chances that we get stack traces from perf going through ffi_call_unix64. This is forward ported from gtk-3-24. # Conflicts: # gtk/gtkeventcontrollerkey.c # gtk/gtkeventcontrollermotion.c # gtk/gtkgesture.c # gtk/gtkgesturemultipress.c
* draggesture: Port to new API modelBenjamin Otte2018-04-261-5/+1
|
* The big versioning cleanupMatthias Clasen2018-02-061-12/+0
| | | | | | | Remove all the old 2.x and 3.x version annotations. GTK+ 4 is a new start, and from the perspective of a GTK+ 4 developer all these APIs have been around since the beginning.
* gesture drag: Use GdkEvent APIMatthias Clasen2017-09-191-1/+3
|
* gesture: Update to using GdkEvent APICarlos Garnacho2017-09-191-1/+1
| | | | To some extent, pad and touchpad gesture events need extra API.
* Various documentation fixesTimm Bäder2016-02-081-2/+2
| | | | | | Always have Since: annotations at the very bottom, use the correct ClassName::signal-name/ClassName:property-name syntax, fix a few typos in type names, wrong function names, non-existing type names, etc.
* Intern all signal names beforehandMatthias Clasen2015-09-121-3/+4
| | | | This avoids pointless allocations
* gtkgesturedrag: Handle touchpad swipe eventsCarlos Garnacho2015-08-121-0/+23
| | | | | These will only trigger the gesture if it's been created with the same GtkGesture::n-points than n_fingers in the event.
* drag: add missing introspection annotationsRay Strode2014-08-061-4/+4
| | | | | | | | | gtk_gesture_drag_get_start_point and gtk_gesture_drag_get_offset have out args that need to be annotated. This commit adds the (out) and (nullable) annotations as appropriate. https://bugzilla.gnome.org/show_bug.cgi?id=734292
* Don't assert in gtk_event_controller_constructedMatthias Clasen2014-05-271-0/+2
| | | | | | This prevents some of our generic object implementation tests from working with gesture objects. Instead, add g_return_if_fail checks in all the gesture constructors.
* Docs: Cosmetic fixesMatthias Clasen2014-05-231-3/+3
|
* drag: Allow gtk_gesture_get_start_point/offset() to be called on ::drag-endCarlos Garnacho2014-05-231-2/+12
|
* Prevent subclassing of gesturesMatthias Clasen2014-05-231-1/+2
| | | | | For now, at least. We do this by hiding the instance and class structures in private headers.
* drag: doc fixesCarlos Garnacho2014-05-231-3/+3
|
* drag: Add missing documentationCarlos Garnacho2014-05-231-0/+44
|
* drag: remove unused #defineCarlos Garnacho2014-05-231-2/+0
|
* drag: Make API offsets basedCarlos Garnacho2014-05-231-12/+21
| | | | | It is generally more useful to get offsets right away, than having to calculate those from the start point.
* drag: Make a subclass of GtkGestureSingleCarlos Garnacho2014-05-231-1/+1
|
* Add GtkGestureDragCarlos Garnacho2014-05-231-0/+210
This gesture interprets and reports drags as an offset to the drag start point.
View Lorry Controller Status