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

New upstream version 3.24.18

Browse Source
This commit is contained in:
Simon McVittie
2020-04-10 15:23:16 +01:00
parent ecf5b7f34b f9decb0cd6
commit ea8a581be2
386 changed files with 78008 additions and 6390 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/reference/gtk/html/chap-input-handling.html
View File

@ -129,7 +129,7 @@
Propagation differs between event types: key events (<code class="literal">GDK_KEY_PRESS</code>,
<code class="literal">GDK_KEY_RELEASE</code>) are delivered to the top-level <a class="link" href="GtkWindow.html" title="GtkWindow"><span class="type">GtkWindow</span></a>; other events
are propagated down and up the widget hierarchy in three phases (see
<a href="https://developer.gnome.org/gtk4/GtkEventController.html#GtkPropagationPhase"><span class="type">GtkPropagationPhase</span></a>).
<a class="link" href="GtkEventController.html#GtkPropagationPhase" title="enum GtkPropagationPhase"><span class="type">GtkPropagationPhase</span></a>).
</p>
<p>
For key events, the top-level window’s default <span class="type">“key-press-event”</span>
@ -144,12 +144,12 @@
delivered to each widget from the top-most (for example, the top-level
<a class="link" href="GtkWindow.html" title="GtkWindow"><span class="type">GtkWindow</span></a> or grab widget) down to the target <a class="link" href="GtkWidget.html" title="GtkWidget"><span class="type">GtkWidget</span></a>.
<a class="link" href="chap-input-handling.html#event-controllers-and-gestures" title="Event controllers and gestures">Gestures</a> that are
attached with <a href="https://developer.gnome.org/gtk4/GtkEventController.html#GTK-PHASE-CAPTURE:CAPS"><code class="literal">GTK_PHASE_CAPTURE</code></a> get a chance to react to the event.
attached with <a class="link" href="GtkEventController.html#GTK-PHASE-CAPTURE:CAPS"><code class="literal">GTK_PHASE_CAPTURE</code></a> get a chance to react to the event.
</p>
<p>
After the “capture” phase, the widget that was intended to be the
destination of the event will run gestures attached to it with
<a href="https://developer.gnome.org/gtk4/GtkEventController.html#GTK-PHASE-TARGET:CAPS"><code class="literal">GTK_PHASE_TARGET</code></a>. This is known as the “target” phase, and only
<a class="link" href="GtkEventController.html#GTK-PHASE-TARGET:CAPS"><code class="literal">GTK_PHASE_TARGET</code></a>. This is known as the “target” phase, and only
happens on that widget.
</p>
<p>
@ -162,7 +162,7 @@
</p>
<p>
The default handlers for the event signals send the event
to gestures that are attached with <a href="https://developer.gnome.org/gtk4/GtkEventController.html#GTK-PHASE-BUBBLE:CAPS"><code class="literal">GTK_PHASE_BUBBLE</code></a>. Therefore,
to gestures that are attached with <a class="link" href="GtkEventController.html#GTK-PHASE-BUBBLE:CAPS"><code class="literal">GTK_PHASE_BUBBLE</code></a>. Therefore,
gestures in the “bubble” phase are only used if the widget does
not have its own event handlers, or takes care to chain up to the
default <a class="link" href="GtkWidget.html" title="GtkWidget"><span class="type">GtkWidget</span></a> handlers.