diff options
| author | Carlos Garnacho <carlosg@gnome.org> | 2017-03-31 18:58:16 +0200 |
|---|---|---|
| committer | Carlos Garnacho <carlosg@gnome.org> | 2017-05-25 16:25:58 +0200 |
| commit | a72404dd5ab1874ac3d601cd94e0fa7184873851 (patch) | |
| tree | b28cd7bb3937ad7f327e7c184ffa65b259179b8d /examples | |
| parent | ef4f0e53364b51efea1d71f7770e8d52631c3cb0 (diff) | |
| download | gtk+-a72404dd5ab1874ac3d601cd94e0fa7184873851.tar.gz | |
gtk: Mass delete all GtkWidget event mask API
We now rely on toplevels receiving and forwarding all the events
the windowing should be able to handle. Event masks are no longer a
way to determine whether an event is deliverable ot a widget.
Events will always be delivered in the three captured/target/bubbled
phases, widgets can now just attach GtkEventControllers and let those
handle the events.
Diffstat (limited to 'examples')
| -rw-r--r-- | examples/drawing.c | 8 |
1 files changed, 0 insertions, 8 deletions
diff --git a/examples/drawing.c b/examples/drawing.c index b5d1114c98..dfd7dbc863 100644 --- a/examples/drawing.c +++ b/examples/drawing.c @@ -162,14 +162,6 @@ activate (GtkApplication *app, g_signal_connect (drawing_area, "button-press-event", G_CALLBACK (button_press_event_cb), NULL); - /* Ask to receive events the drawing area doesn't normally - * subscribe to. In particular, we need to ask for the - * button press and motion notify events that want to handle. - */ - gtk_widget_set_events (drawing_area, gtk_widget_get_events (drawing_area) - | GDK_BUTTON_PRESS_MASK - | GDK_POINTER_MOTION_MASK); - gtk_widget_show (window); } |