| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
And use it to handle kinetic scrolling in the GtkScrolledWindow.
However, dropping the delta check causes the X11-based kinetic
scroll to break since we don't have the stop event here. Correct handling of
xf86-input-libinput-based scroll events is still being discussed.
https://bugzilla.gnome.org/show_bug.cgi?id=756729
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=759309
|
|
|
|
|
|
|
|
| |
Each gesture type has its separate GdkEvent struct, and begin/update/
end/cancel event types.
There is support for multi-finger swipe (3-4 fingers), and 2-finger
rotate/pinch gestures.
|
|
|
|
|
| |
We don't support multiple screens anymore, so there is no need
for marking API as multihead safe any longer.
|
|
|
|
| |
Not much to copy nor free, but this'll make bindings happy
|
|
|
|
|
| |
It has been replaced by GdkRGBA. Time to make it official.
http://bugzilla.gnome.org/show_bug.cgi?id=636695
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=729983
|
|
|
|
|
|
| |
These don't really work anymore in a composited world.
Lets make it official.
https://bugzilla.gnome.org/show_bug.cgi?id=481073
|
| |
|
| |
|
|
|
|
| |
https://wiki.gnome.org/Design/OS/Typography
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=723119
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=723119
|
|
|
|
| |
Use # syntax where appropriate.
|
| |
|
| |
|
|
|
|
|
| |
Refers to an uncommitted part of
https://bugzilla.gnome.org/show_bug.cgi?id=696001
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
It's too easy getting bitten by the ->device red herring, thinking
that it's the original input device the event originated from.
https://bugzilla.gnome.org/show_bug.cgi?id=709621
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=707844
|
|
|
|
|
|
|
| |
This is useful for language bindings, who can't easily
access the struct field directly.
https://bugzilla.gnome.org/show_bug.cgi?id=700029
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=701463
|
|
|
|
|
|
| |
This information is needed to draw client-side decorations
properly in this state.
https://bugzilla.gnome.org/show_bug.cgi?id=696001
|
|
|
|
|
| |
This is in preparation to modernizing our handing
of exported symbols.
|
|
|
|
|
|
| |
gcc has optimizations for include guards that only work
if they are outermost in the the header.
https://bugzilla.gnome.org/show_bug.cgi?id=689810
|
|
|
|
|
|
| |
Its 'state' field is of type GdkPropertyState.
https://bugzilla.gnome.org/show_bug.cgi?id=677775
|
|
|
|
|
|
|
| |
The things related to touch and smooth scrolling were 3.4 additions,
so mark them as such.
https://bugzilla.gnome.org/show_bug.cgi?id=676329
|
|
|
|
|
|
|
|
|
| |
GDK_EVENT_2BUTTON_PRESS and GDK_EVENT_3BUTTON_PRESS can't be used from
some bindings because they'd translate to something syntactically
invalid. Add GDK_EVENT_DOUBLE_BUTTON_PRESS and
GDK_EVENT_TRIPLE_BUTTON_PRESS aliases to work around that.
https://bugzilla.gnome.org/show_bug.cgi?id=671025
|
| |
|
|
|
|
|
| |
gdk_event_get_scroll_deltas() can be used to retrieve those
values on smooth scroll events.
|
|
|
|
|
| |
This value will be used for smooth scroll events, as they'll
express the scrolling direction in terms of dx/dy.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Anytime a touch device interacts, the crossing events generation
will change to a touch mode where only events with mode
GDK_CROSSING_TOUCH_BEGIN/END are handled, and those are sent
around touch begin/end. Those are virtual as the master
device may still stay on the window.
Whenever there is a switch of slave device (the user starts
using another non-touch device), a crossing event with mode
GDK_CROSSING_DEVICE_SWITCH may generated if needed, and the normal
crossing event handling is resumed.
|
|
|
|
|
|
|
| |
This commit introduces GDK_TOUCH_BEGIN/UPDATE/END/CANCEL
and a separate GdkEventTouch struct that they use. This
is closer to the touch event API of other platforms and
matches the xi2 events closely, too.
|
|
|
|
|
| |
GdkEventSequence is an opaque pointer type that is used
to identify sequences of touch events that belong together.
|
| |
|
|
|
|
|
|
|
| |
This patch changes all uses of GDK_DEPRECATED(_FOR) in gdk headers
by the versioned variants, GDK_DEPRECATED_IN_3_x(_FOR). At the same
time, we add GDK_AVAILABLE_IN_3_x annotations for all API additions
in 3.2 and 3.4.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=668688
|
|
|
|
|
|
|
|
|
|
|
| |
Similar to https://bugzilla.gnome.org/show_bug.cgi?id=631413 in GLib,
GTK+ should have symbolic constants for controlling the event handling
instead of a mere boolean value.
The GDK_EVENT_PROPAGATE and GDK_EVENT_STOP constants map to FALSE and
TRUE respectively.
https://bugzilla.gnome.org/show_bug.cgi?id=631414
|
|
|
|
|
|
|
|
|
|
| |
This state means that the toplevel window is presented as focused to the user,
i.e with active decorations under an X11 window manager.
If the GDK backend doesn't implement this flag, it will just remain set after
mapping the window.
https://bugzilla.gnome.org/show_bug.cgi?id=661428
|
|
|
|
|
|
| |
Add gdk_event_triggers_context_menu(), using the new modifier
abstraction API. Remove _gtk_button_event_triggers_context_menu()
and port all callers.
|
|
|
|
|
|
|
| |
Add accessors for the following fields: button, keyval, keycode, scroll
direction, click count.
https://bugzilla.gnome.org/show_bug.cgi?id=657384
|
|
|
|
|
| |
instead of a GdkNativeWindow. Also change gdk_selection_notify() API to
take a GdkWindow to match this change.
|