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

New upstream version 3.24.14

Browse Source
This commit is contained in:
Simon McVittie
2020-02-29 14:17:40 +00:00
parent ffccf14831 fab213a5f9
commit 701099732f
543 changed files with 330694 additions and 808714 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -8,7 +8,7 @@
<link rel="up" href="gtk.html" title="Part I. GTK+ Overview">
<link rel="prev" href="chap-drawing-model.html" title="The GTK+ Drawing Model">
<link rel="next" href="gtkobjects.html" title="Part II. GTK+ Widgets and Objects">
<meta name="generator" content="GTK-Doc V1.29 (XML mode)">
<meta name="generator" content="GTK-Doc V1.32.1 (XML mode)">
<link rel="stylesheet" href="style.css" type="text/css">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@ -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 class="link" href="GtkEventController.html#GtkPropagationPhase" title="enum GtkPropagationPhase"><span class="type">GtkPropagationPhase</span></a>).
<a href="https://developer.gnome.org/gtk4/GtkEventController.html#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 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.
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.
</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 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
<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
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 class="link" href="GtkEventController.html#GTK-PHASE-BUBBLE:CAPS"><code class="literal">GTK_PHASE_BUBBLE</code></a>. Therefore,
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,
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.
@ -352,6 +352,6 @@
</div>
</div>
<div class="footer">
<hr>Generated by GTK-Doc V1.29</div>
<hr>Generated by GTK-Doc V1.32.1</div>
</body>
</html>