From 4ae95157ae328fd625802624961e91f7dde281c7 Mon Sep 17 00:00:00 2001 From: Matthias Clasen Date: Mon, 26 May 2014 10:17:07 -0400 Subject: [PATCH] docs: remove markup The overview chapters don't go through shorthand processing, so don't use them there. --- docs/reference/gtk/input-handling.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/reference/gtk/input-handling.xml b/docs/reference/gtk/input-handling.xml index 91c4f7f227..4806b9e3c4 100644 --- a/docs/reference/gtk/input-handling.xml +++ b/docs/reference/gtk/input-handling.xml @@ -91,7 +91,7 @@ The event is then propagated from the toplevel window down to the target widget. In this phase, which is known as the “capture” phase, - gestures that are attached with %GTK_PHASE_CAPTURE get a chance + gestures that are attached with GTK_PHASE_CAPTURE get a chance to react to the event. @@ -101,12 +101,12 @@ way to handle input in GTK+ widgets before gestures were introduced. The signals are emitted from the target widget up to the toplevel, until a signal handler indicates that it has handled the event, by - returning %GDK_EVENT_STOP. + returning GDK_EVENT_STOP. The default handlers for the event signals send the event - to gestures that are attached with %GTK_PHASE_TARGET. Therefore, + to gestures that are attached with GTK_PHASE_TARGET. Therefore, gestures in the ”target” phase are only used if the widget does not have its own event handlers, or takes care to chain up to the default handlers. @@ -114,7 +114,7 @@ After calling the event handlers, in the so-called ”bubble” phase, - gestures that are attached with %GTK_PHASE_BUBBLE get a chance + gestures that are attached with GTK_PHASE_BUBBLE get a chance to react to the event.