callisto-debian/gtk3
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: remove markup

Browse Source 
The overview chapters don't go through shorthand processing, so
don't use them there.
This commit is contained in:
Matthias Clasen
2014-05-26 10:17:07 -04:00
parent 750f6b9913
commit 4ae95157ae
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/reference/gtk/input-handling.xml
View File

@ -91,7 +91,7 @@
<para>
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.
</para>
@ -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.
</para>
<para>
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 @@
<para>
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.
</para>