RubyGems - gdk3 - Versions diffs - 3.2.1-x86-mingw32 → 3.2.2-x86-mingw32 - Mend

gdk3 3.2.1-x86-mingw32 → 3.2.2-x86-mingw32

Files changed (2767) hide show

data/vendor/local/share/gtk-doc/html/gtk3/chap-drawing-model.html CHANGED Viewed

@@ -8,7 +8,7 @@
 <link rel="up" href="gtk.html" title="Part I. GTK+ Overview">
 <link rel="prev" href="gtk-question-index.html" title="Common Questions">
 <link rel="next" href="chap-input-handling.html" title="The GTK+ Input and Event Handling Model">
-<meta name="generator" content="GTK-Doc V1.25.1 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.27 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -92,7 +92,7 @@
 <p>
         The windowing system generates events for native windows. The GDK
         interface to the windowing system translates such native events into
-        <a href="../gdk4/gdk4-Event-Structures.html#GdkEvent"><span class="structname">GdkEvent</span></a>
+        <a href="../html/gdk3-Event-Structures.html#GdkEvent"><span class="structname">GdkEvent</span></a>
         structures and sends them on to the GTK layer.  In turn, the GTK layer
         finds the widget that corresponds to a particular
         <code class="classname">GdkWindow</code> and emits the corresponding event
@@ -318,15 +318,15 @@
 7
 8
 9</pre></td>
-        <td class="listing_code"><pre class="programlisting"><span class="gtkdoc kwb">static void</span>
-<span class="function">my_widget_init</span> <span class="gtkdoc opt">(</span>MyWidget <span class="gtkdoc opt">*</span>widget<span class="gtkdoc opt">)</span>
-<span class="gtkdoc opt">{</span>
-  <span class="gtkdoc opt">...</span>
+        <td class="listing_code"><pre class="programlisting"><span class="keyword">static</span><span class="normal"> </span><span class="type">void</span>
+<span class="function">my_widget_init</span><span class="normal"> </span><span class="symbol">(</span><span class="usertype">MyWidget</span><span class="normal"> </span><span class="symbol">*</span><span class="normal">widget</span><span class="symbol">)</span>
+<span class="cbracket">{</span>
+<span class="normal">  </span><span class="symbol">...</span>
-  <span class="function"><a href="GtkWidget.html#gtk-widget-set-double-buffered">gtk_widget_set_double_buffered</a></span> <span class="gtkdoc opt">(</span>widget<span class="gtkdoc opt">,</span> FALSE<span class="gtkdoc opt">);</span>
+<span class="normal">  </span><span class="function"><a href="GtkWidget.html#gtk-widget-set-double-buffered">gtk_widget_set_double_buffered</a></span><span class="normal"> </span><span class="symbol">(</span><span class="normal">widget</span><span class="symbol">,</span><span class="normal"> FALSE</span><span class="symbol">);</span>
-  <span class="gtkdoc opt">...</span>
-<span class="gtkdoc opt">}</span></pre></td>
+<span class="normal">  </span><span class="symbol">...</span>
+<span class="cbracket">}</span></pre></td>
       </tr>
     </tbody>
   </table>
@@ -413,6 +413,6 @@
 </div>
 </div>
 <div class="footer">
-<hr>Generated by GTK-Doc V1.25.1</div>
+<hr>Generated by GTK-Doc V1.27</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/gtk3/chap-input-handling.html CHANGED Viewed

@@ -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.25.1 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.27 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -44,7 +44,7 @@
      The most basic input devices that every computer user has interacted with are
      keyboards and mice; beyond these, GTK+ supports touchpads, touchscreens and
      more exotic input devices such as graphics tablets. Inside GTK+, every such
-     input device is represented by a <a href="../gdk4/GdkDevice.html#GdkDevice-struct"><span class="type">GdkDevice</span></a> object.
+     input device is represented by a <a href="../html/GdkDevice.html#GdkDevice-struct"><span class="type">GdkDevice</span></a> object.
     </p>
 <p>
      To simplify dealing with the variability between these input devices, GTK+
@@ -67,16 +67,16 @@
      the window with the keyboard focus.
     </p>
 <p>
-     GDK translates these raw windowing system events into <a href="../gdk4/gdk4-Event-Structures.html#GdkEvent"><span class="type">GdkEvents</span></a>.
+     GDK translates these raw windowing system events into <a href="../html/gdk3-Event-Structures.html#GdkEvent"><span class="type">GdkEvents</span></a>.
      Typical input events are:
      </p>
 <table border="0" summary="Simple list" class="simplelist">
-<tr><td><a href="../gdk4/gdk4-Event-Structures.html#GdkEventButton"><span class="type">GdkEventButton</span></a></td></tr>
-<tr><td><a href="../gdk4/gdk4-Event-Structures.html#GdkEventMotion"><span class="type">GdkEventMotion</span></a></td></tr>
-<tr><td><a href="../gdk4/gdk4-Event-Structures.html#GdkEventCrossing"><span class="type">GdkEventCrossing</span></a></td></tr>
-<tr><td><a href="../gdk4/gdk4-Event-Structures.html#GdkEventKey"><span class="type">GdkEventKey</span></a></td></tr>
-<tr><td><a href="../gdk4/gdk4-Event-Structures.html#GdkEventFocus"><span class="type">GdkEventFocus</span></a></td></tr>
-<tr><td><a href="../gdk4/gdk4-Event-Structures.html#GdkEventTouch"><span class="type">GdkEventTouch</span></a></td></tr>
+<tr><td><a href="../html/gdk3-Event-Structures.html#GdkEventButton"><span class="type">GdkEventButton</span></a></td></tr>
+<tr><td><a href="../html/gdk3-Event-Structures.html#GdkEventMotion"><span class="type">GdkEventMotion</span></a></td></tr>
+<tr><td><a href="../html/gdk3-Event-Structures.html#GdkEventCrossing"><span class="type">GdkEventCrossing</span></a></td></tr>
+<tr><td><a href="../html/gdk3-Event-Structures.html#GdkEventKey"><span class="type">GdkEventKey</span></a></td></tr>
+<tr><td><a href="../html/gdk3-Event-Structures.html#GdkEventFocus"><span class="type">GdkEventFocus</span></a></td></tr>
+<tr><td><a href="../html/gdk3-Event-Structures.html#GdkEventTouch"><span class="type">GdkEventTouch</span></a></td></tr>
 </table>
 <p>
     </p>
@@ -85,14 +85,14 @@
       grabs (system-wide or in-app) are taking input away:
       </p>
 <table border="0" summary="Simple list" class="simplelist">
-<tr><td><a href="../gdk4/gdk4-Event-Structures.html#GdkEventGrabBroken"><span class="type">GdkEventGrabBroken</span></a></td></tr>
+<tr><td><a href="../html/gdk3-Event-Structures.html#GdkEventGrabBroken"><span class="type">GdkEventGrabBroken</span></a></td></tr>
 <tr><td><a class="link" href="GtkWidget.html#GtkWidget-grab-notify" title="The “grab-notify” signal"><span class="type">“grab-notify”</span></a></td></tr>
 </table>
 <p>
     </p>
 <p>
       When GTK+ is initialized, it sets up an event handler function with
-      <a href="../gdk4/gdk4-Events.html#gdk-event-handler-set"><code class="function">gdk_event_handler_set()</code></a>, which receives all of these input events
+      <a href="../html/gdk3-Events.html#gdk-event-handler-set"><code class="function">gdk_event_handler_set()</code></a>, which receives all of these input events
       (as well as others, for instance window management related events).
     </p>
 </div>
@@ -100,7 +100,7 @@
 <div class="refsect2">
 <a name="event-propagation"></a><h3>Event propagation</h3>
 <p>
-      For widgets which have a <a href="../gdk4/gdk4-Windows.html#GdkWindow-struct"><span class="type">GdkWindow</span></a> set, events are received from the
+      For widgets which have a <a href="../html/gdk3-Windows.html#GdkWindow-struct"><span class="type">GdkWindow</span></a> set, events are received from the
       windowing system and passed to <a class="link" href="gtk3-General.html#gtk-main-do-event" title="gtk_main_do_event ()"><code class="function">gtk_main_do_event()</code></a>. See its documentation
       for details of what it does: compression of enter/leave events,
       identification of the widget receiving the event, pushing the event onto a
@@ -108,26 +108,26 @@
       widget.
     </p>
 <p>
-      When a GDK backend produces an input event, it is tied to a <a href="../gdk4/GdkDevice.html#GdkDevice-struct"><span class="type">GdkDevice</span></a> and
-      a <a href="../gdk4/gdk4-Windows.html#GdkWindow-struct"><span class="type">GdkWindow</span></a>, which in turn represents a windowing system surface in the
+      When a GDK backend produces an input event, it is tied to a <a href="../html/GdkDevice.html#GdkDevice-struct"><span class="type">GdkDevice</span></a> and
+      a <a href="../html/gdk3-Windows.html#GdkWindow-struct"><span class="type">GdkWindow</span></a>, which in turn represents a windowing system surface in the
       backend. If a widget has grabbed the current input device, or all input
       devices, the event is propagated to that <a class="link" href="GtkWidget.html" title="GtkWidget"><span class="type">GtkWidget</span></a>. Otherwise, it is
       propagated to the the <a class="link" href="GtkWidget.html" title="GtkWidget"><span class="type">GtkWidget</span></a> which called <a class="link" href="GtkWidget.html#gtk-widget-register-window" title="gtk_widget_register_window ()"><code class="function">gtk_widget_register_window()</code></a>
-      on the <a href="../gdk4/gdk4-Windows.html#GdkWindow-struct"><span class="type">GdkWindow</span></a> receiving the event.
+      on the <a href="../html/gdk3-Windows.html#GdkWindow-struct"><span class="type">GdkWindow</span></a> receiving the event.
     </p>
 <p>
       Grabs are implemented for each input device, and globally. A grab for a
       specific input device (<a class="link" href="gtk3-General.html#gtk-device-grab-add" title="gtk_device_grab_add ()"><code class="function">gtk_device_grab_add()</code></a>), is sent events in
       preference to a global grab (<a class="link" href="gtk3-General.html#gtk-grab-add" title="gtk_grab_add ()"><code class="function">gtk_grab_add()</code></a>). Input grabs only have effect
       within the <a class="link" href="GtkWindowGroup.html" title="GtkWindowGroup"><span class="type">GtkWindowGroup</span></a> containing the <a class="link" href="GtkWidget.html" title="GtkWidget"><span class="type">GtkWidget</span></a> which registered the
-      event’s <a href="../gdk4/gdk4-Windows.html#GdkWindow-struct"><span class="type">GdkWindow</span></a>. If this <a class="link" href="GtkWidget.html" title="GtkWidget"><span class="type">GtkWidget</span></a> is a child of the grab widget, the
+      event’s <a href="../html/gdk3-Windows.html#GdkWindow-struct"><span class="type">GdkWindow</span></a>. If this <a class="link" href="GtkWidget.html" title="GtkWidget"><span class="type">GtkWidget</span></a> is a child of the grab widget, the
       event is propagated to the child — this is the basis for propagating
       events within modal dialogs.
     </p>
 <p>
       An event is propagated to a widget using <a class="link" href="gtk3-General.html#gtk-propagate-event" title="gtk_propagate_event ()"><code class="function">gtk_propagate_event()</code></a>.
-      Propagation differs between event types: key events (<a href="../gdk4/gdk4-Events.html#GDK-KEY-PRESS:CAPS"><code class="literal">GDK_KEY_PRESS</code></a>,
-      <a href="../gdk4/gdk4-Events.html#GDK-KEY-RELEASE:CAPS"><code class="literal">GDK_KEY_RELEASE</code></a>) are delivered to the top-level <a class="link" href="GtkWindow.html" title="GtkWindow"><span class="type">GtkWindow</span></a>; other events
+      Propagation differs between event types: key events (<a href="../html/gdk3-Events.html#GDK-KEY-PRESS:CAPS"><code class="literal">GDK_KEY_PRESS</code></a>,
+      <a href="../html/gdk3-Events.html#GDK-KEY-RELEASE:CAPS"><code class="literal">GDK_KEY_RELEASE</code></a>) 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>).
     </p>
@@ -173,7 +173,7 @@
 <p>
       Any time during the propagation phase, a widget may indicate that a
       received event was consumed and propagation should therefore be stopped.
-      In traditional event handlers, this is hinted by returning <a href="../gdk4/gdk4-Events.html#GDK-EVENT-STOP:CAPS"><code class="literal">GDK_EVENT_STOP</code></a>.
+      In traditional event handlers, this is hinted by returning <a href="../html/gdk3-Events.html#GDK-EVENT-STOP:CAPS"><code class="literal">GDK_EVENT_STOP</code></a>.
       If gestures are used, this may happen when the widget tells the gesture
       to claim the event touch sequence (or the pointer events) for its own. See the
       "gesture states" section below to know more of the latter.
@@ -186,21 +186,21 @@
       Each widget instance has a basic event mask and another per input device,
       which determine the types of input event it receives. Each event mask set
       on a widget is added to the corresponding (basic or per-device) event mask
-      for the widget’s <a href="../gdk4/gdk4-Windows.html#GdkWindow-struct"><span class="type">GdkWindow</span></a>, and all child <a href="../gdk4/gdk4-Windows.html#GdkWindow-struct"><span class="type">GdkWindows</span></a>.
+      for the widget’s <a href="../html/gdk3-Windows.html#GdkWindow-struct"><span class="type">GdkWindow</span></a>, and all child <a href="../html/gdk3-Windows.html#GdkWindow-struct"><span class="type">GdkWindows</span></a>.
     </p>
 <p>
-      If a widget is windowless (<a class="link" href="GtkWidget.html#gtk-widget-get-has-window" title="gtk_widget_get_has_window ()"><code class="function">gtk_widget_get_has_window()</code></a> returns <a href="/home/vagrant/ruby-gnome2.win32/glib2/vendor/local/share/gtk-doc/html/glib/glib-Standard-Macros.html#FALSE:CAPS"><code class="literal">FALSE</code></a>) and
+      If a widget is windowless (<a class="link" href="GtkWidget.html#gtk-widget-get-has-window" title="gtk_widget_get_has_window ()"><code class="function">gtk_widget_get_has_window()</code></a> returns <code class="literal">FALSE</code>) and
       an application wants to receive custom events on it, it must be placed
       inside a <a class="link" href="GtkEventBox.html" title="GtkEventBox"><span class="type">GtkEventBox</span></a> to receive the events, and an appropriate event mask
-      must be set on the box. When implementing a widget, use a <a href="../gdk4/gdk4-Windows.html#GDK-INPUT-ONLY:CAPS"><code class="literal">GDK_INPUT_ONLY</code></a>
-      <a href="../gdk4/gdk4-Windows.html#GdkWindow-struct"><span class="type">GdkWindow</span></a> to receive the events instead.
+      must be set on the box. When implementing a widget, use a <a href="../html/gdk3-Windows.html#GDK-INPUT-ONLY:CAPS"><code class="literal">GDK_INPUT_ONLY</code></a>
+      <a href="../html/gdk3-Windows.html#GdkWindow-struct"><span class="type">GdkWindow</span></a> to receive the events instead.
     </p>
 <p>
-      Filtering events against event masks happens inside <a href="../gdk4/gdk4-Windows.html#GdkWindow-struct"><span class="type">GdkWindow</span></a>, which
+      Filtering events against event masks happens inside <a href="../html/gdk3-Windows.html#GdkWindow-struct"><span class="type">GdkWindow</span></a>, which
       exposes event masks to the windowing system to reduce the number of events
       GDK receives from it. On receiving an event, it is filtered against the
-      <a href="../gdk4/gdk4-Windows.html#GdkWindow-struct"><span class="type">GdkWindow</span></a>’s mask for the input device, if set. Otherwise, it is filtered
-      against the <a href="../gdk4/gdk4-Windows.html#GdkWindow-struct"><span class="type">GdkWindow</span></a>’s basic event mask.
+      <a href="../html/gdk3-Windows.html#GdkWindow-struct"><span class="type">GdkWindow</span></a>’s mask for the input device, if set. Otherwise, it is filtered
+      against the <a href="../html/gdk3-Windows.html#GdkWindow-struct"><span class="type">GdkWindow</span></a>’s basic event mask.
     </p>
 <p>
       This means that widgets must add to the event mask for each event type
@@ -208,7 +208,7 @@
       <a class="link" href="GtkWidget.html#gtk-widget-add-events" title="gtk_widget_add_events ()"><code class="function">gtk_widget_add_events()</code></a> to preserve the existing mask. Widgets which are
       aware of floating devices should use <a class="link" href="GtkWidget.html#gtk-widget-set-device-events" title="gtk_widget_set_device_events ()"><code class="function">gtk_widget_set_device_events()</code></a> or
       <a class="link" href="GtkWidget.html#gtk-widget-add-device-events" title="gtk_widget_add_device_events ()"><code class="function">gtk_widget_add_device_events()</code></a>, and must explicitly enable the device
-      using <a class="link" href="GtkWidget.html#gtk-widget-set-device-enabled" title="gtk_widget_set_device_enabled ()"><code class="function">gtk_widget_set_device_enabled()</code></a>. See the <a href="../gdk4/GdkDeviceManager.html#GdkDeviceManager-struct"><span class="type">GdkDeviceManager</span></a>
+      using <a class="link" href="GtkWidget.html#gtk-widget-set-device-enabled" title="gtk_widget_set_device_enabled ()"><code class="function">gtk_widget_set_device_enabled()</code></a>. See the <a href="../html/GdkDeviceManager.html#GdkDeviceManager-struct"><span class="type">GdkDeviceManager</span></a>
       documentation for more information.
     </p>
 <p>
@@ -221,23 +221,23 @@
 <div class="refsect2">
 <a name="id-1.2.7.3.6"></a><h3>Touch events</h3>
 <p>
-      Touch events are emitted as events of type <a href="../gdk4/gdk4-Events.html#GDK-TOUCH-BEGIN:CAPS"><code class="literal">GDK_TOUCH_BEGIN</code></a>, <a href="../gdk4/gdk4-Events.html#GDK-TOUCH-UPDATE:CAPS"><code class="literal">GDK_TOUCH_UPDATE</code></a> or
-      <a href="../gdk4/gdk4-Events.html#GDK-TOUCH-END:CAPS"><code class="literal">GDK_TOUCH_END</code></a>, those events contain an “event sequence” that univocally identifies
+      Touch events are emitted as events of type <a href="../html/gdk3-Events.html#GDK-TOUCH-BEGIN:CAPS"><code class="literal">GDK_TOUCH_BEGIN</code></a>, <a href="../html/gdk3-Events.html#GDK-TOUCH-UPDATE:CAPS"><code class="literal">GDK_TOUCH_UPDATE</code></a> or
+      <a href="../html/gdk3-Events.html#GDK-TOUCH-END:CAPS"><code class="literal">GDK_TOUCH_END</code></a>, those events contain an “event sequence” that univocally identifies
       the physical touch until it is lifted from the device.
     </p>
 <p>
       On some windowing platforms, multitouch devices perform pointer emulation, this works
       by granting a “pointer emulating” hint to one of the currently interacting touch
-      sequences, which will be reported on every <a href="../gdk4/gdk4-Event-Structures.html#GdkEventTouch"><span class="type">GdkEventTouch</span></a> event from that sequence. By
-      default, if a widget didn't request touch events by setting <a href="../gdk4/gdk4-Events.html#GDK-TOUCH-MASK:CAPS"><code class="literal">GDK_TOUCH_MASK</code></a> on its
+      sequences, which will be reported on every <a href="../html/gdk3-Event-Structures.html#GdkEventTouch"><span class="type">GdkEventTouch</span></a> event from that sequence. By
+      default, if a widget didn't request touch events by setting <a href="../html/gdk3-Events.html#GDK-TOUCH-MASK:CAPS"><code class="literal">GDK_TOUCH_MASK</code></a> on its
       event mask and didn't override <a class="link" href="GtkWidget.html#GtkWidget-touch-event" title="The “touch-event” signal"><span class="type">“touch-event”</span></a>, GTK+ will transform these
-      “pointer emulating” events into semantically similar <a href="../gdk4/gdk4-Event-Structures.html#GdkEventButton"><span class="type">GdkEventButton</span></a> and <a href="../gdk4/gdk4-Event-Structures.html#GdkEventMotion"><span class="type">GdkEventMotion</span></a>
-      events. Depending on <a href="../gdk4/gdk4-Events.html#GDK-TOUCH-MASK:CAPS"><code class="literal">GDK_TOUCH_MASK</code></a> being in the event mask or not, non-pointer-emulating
+      “pointer emulating” events into semantically similar <a href="../html/gdk3-Event-Structures.html#GdkEventButton"><span class="type">GdkEventButton</span></a> and <a href="../html/gdk3-Event-Structures.html#GdkEventMotion"><span class="type">GdkEventMotion</span></a>
+      events. Depending on <a href="../html/gdk3-Events.html#GDK-TOUCH-MASK:CAPS"><code class="literal">GDK_TOUCH_MASK</code></a> being in the event mask or not, non-pointer-emulating
       sequences could still trigger gestures or just get filtered out, regardless of the widget
       not handling those directly.
     </p>
 <p>
-      If the widget sets <a href="../gdk4/gdk4-Events.html#GDK-TOUCH-MASK:CAPS"><code class="literal">GDK_TOUCH_MASK</code></a> on its event mask and doesn't chain up on
+      If the widget sets <a href="../html/gdk3-Events.html#GDK-TOUCH-MASK:CAPS"><code class="literal">GDK_TOUCH_MASK</code></a> on its event mask and doesn't chain up on
       <a class="link" href="GtkWidget.html#GtkWidget-touch-event" title="The “touch-event” signal"><span class="type">“touch-event”</span></a>, only touch events will be received, and no pointer emulation
       will be performed.
     </p>
@@ -251,8 +251,8 @@
       happen on user interaction, when a <span class="type">GdkEventButtonPress</span> happens, all events from
       then on, until after the corresponding <span class="type">GdkEventButtonRelease</span>, will be reported
       to the widget that got the first event. Likewise, on touch events, every
-      <a href="../gdk4/gdk4-Events.html#GdkEventSequence"><span class="type">GdkEventSequence</span></a> will deliver only events to the widget that received its
-      <a href="../gdk4/gdk4-Events.html#GDK-TOUCH-BEGIN:CAPS"><code class="literal">GDK_TOUCH_BEGIN</code></a> event.
+      <a href="../html/gdk3-Events.html#GdkEventSequence"><span class="type">GdkEventSequence</span></a> will deliver only events to the widget that received its
+      <a href="../html/gdk3-Events.html#GDK-TOUCH-BEGIN:CAPS"><code class="literal">GDK_TOUCH_BEGIN</code></a> event.
     </p>
 <p>
       Explicit grabs happen programatically (both activation and deactivation),
@@ -268,7 +268,7 @@
       This makes it necessary for widgets to handle the cancellation of any ongoing
       interaction. Depending on whether a GTK or GDK grab is causing this, the
       widget will respectively receive a <a class="link" href="GtkWidget.html#GtkWidget-grab-notify" title="The “grab-notify” signal"><span class="type">“grab-notify”</span></a> signal, or a
-      <a href="../gdk4/gdk4-Event-Structures.html#GdkEventGrabBroken"><span class="type">GdkEventGrabBroken</span></a> event.
+      <a href="../html/gdk3-Event-Structures.html#GdkEventGrabBroken"><span class="type">GdkEventGrabBroken</span></a> event.
     </p>
 <p>
       On gestures, these signals are handled automatically, causing the gesture
@@ -284,7 +284,7 @@
 <a name="event-controllers-and-gestures"></a><h3>Event controllers and gestures</h3>
 <p>
       Event controllers are standalone objects that can perform specific actions
-      upon received <a href="../gdk4/gdk4-Event-Structures.html#GdkEvent"><span class="type">GdkEvents</span></a>. These are tied to a <a class="link" href="GtkWidget.html" title="GtkWidget"><span class="type">GtkWidget</span></a>, and can be told of
+      upon received <a href="../html/gdk3-Event-Structures.html#GdkEvent"><span class="type">GdkEvents</span></a>. These are tied to a <a class="link" href="GtkWidget.html" title="GtkWidget"><span class="type">GtkWidget</span></a>, and can be told of
       the event propagation phase at which they will manage the events.
     </p>
 <p>
@@ -338,7 +338,7 @@
       Alternatively, or at a later point in time, the widget may choose to deny the touch
       sequences, thus letting those go through again in event propagation. When this happens
       in the capture phase, and if there are no other claiming gestures in the widget,
-      a <a href="../gdk4/gdk4-Events.html#GDK-TOUCH-BEGIN:CAPS"><code class="literal">GDK_TOUCH_BEGIN</code></a>/<a href="../gdk4/gdk4-Events.html#GDK-BUTTON-PRESS:CAPS"><code class="literal">GDK_BUTTON_PRESS</code></a> event will be emulated and
+      a <a href="../html/gdk3-Events.html#GDK-TOUCH-BEGIN:CAPS"><code class="literal">GDK_TOUCH_BEGIN</code></a>/<a href="../html/gdk3-Events.html#GDK-BUTTON-PRESS:CAPS"><code class="literal">GDK_BUTTON_PRESS</code></a> event will be emulated and
       propagated downwards, in order to preserve consistency.
     </p>
 <p>
@@ -352,6 +352,6 @@
 </div>
 </div>
 <div class="footer">
-<hr>Generated by GTK-Doc V1.25.1</div>
+<hr>Generated by GTK-Doc V1.27</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/gtk3/checklist-gdkeventexpose-region.html CHANGED Viewed

@@ -8,7 +8,7 @@
 <link rel="up" href="gtk-migrating-checklist.html" title="Migration Details Checklist">
 <link rel="prev" href="gtk-migrating-checklist.html" title="Migration Details Checklist">
 <link rel="next" href="checklist-modifiers.html" title="Test for modifier keys correctly">
-<meta name="generator" content="GTK-Doc V1.25.1 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.27 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -76,6 +76,6 @@ my_widget_expose_event_handler (GtkWidget *widget, GdkEventExpose *event)
     </pre>
 </div>
 <div class="footer">
-<hr>Generated by GTK-Doc V1.25.1</div>
+<hr>Generated by GTK-Doc V1.27</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/gtk3/checklist-modifiers.html CHANGED Viewed

@@ -8,7 +8,7 @@
 <link rel="up" href="gtk-migrating-checklist.html" title="Migration Details Checklist">
 <link rel="prev" href="checklist-gdkeventexpose-region.html" title="Use GdkEventExpose.region">
 <link rel="next" href="checklist-named-icons.html" title="Use named icons">
-<meta name="generator" content="GTK-Doc V1.25.1 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.27 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -83,6 +83,6 @@ my_widget_key_press_event_handler (GtkWidget *widget, GdkEventKey *event)
     </pre>
 </div>
 <div class="footer">
-<hr>Generated by GTK-Doc V1.25.1</div>
+<hr>Generated by GTK-Doc V1.27</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/gtk3/checklist-named-icons.html CHANGED Viewed

@@ -8,7 +8,7 @@
 <link rel="up" href="gtk-migrating-checklist.html" title="Migration Details Checklist">
 <link rel="prev" href="checklist-modifiers.html" title="Test for modifier keys correctly">
 <link rel="next" href="gtk-migrating-3-x-to-y.html" title="Migrating from one GTK+ 3 release to another">
-<meta name="generator" content="GTK-Doc V1.25.1 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.27 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -34,6 +34,6 @@
     </p>
 </div>
 <div class="footer">
-<hr>Generated by GTK-Doc V1.25.1</div>
+<hr>Generated by GTK-Doc V1.27</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/gtk3/glossary.html CHANGED Viewed

@@ -8,7 +8,7 @@
 <link rel="up" href="index.html" title="GTK+ 3 Reference Manual">
 <link rel="prev" href="gtk-mir.html" title="Using GTK+ with Mir">
 <link rel="next" href="api-index-full.html" title="Index of all symbols">
-<meta name="generator" content="GTK-Doc V1.25.1 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.27 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -327,6 +327,6 @@
 </dl>
 </div>
 <div class="footer">
-<hr>Generated by GTK-Doc V1.25.1</div>
+<hr>Generated by GTK-Doc V1.27</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/gtk3/gtk-broadway.html CHANGED Viewed

@@ -8,7 +8,7 @@
 <link rel="up" href="platform-support.html" title="Part VII. GTK+ Platform Support">
 <link rel="prev" href="gtk-osx.html" title="Using GTK+ on Mac OS X">
 <link rel="next" href="gtk-wayland.html" title="Using GTK+ with Wayland">
-<meta name="generator" content="GTK-Doc V1.25.1 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.27 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -80,6 +80,6 @@ GDK_BACKEND=broadway BROADWAY_DISPLAY=:5 gtk3-demo
 </div>
 </div>
 <div class="footer">
-<hr>Generated by GTK-Doc V1.25.1</div>
+<hr>Generated by GTK-Doc V1.27</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/gtk3/gtk-builder-tool.html CHANGED Viewed

@@ -8,7 +8,7 @@
 <link rel="up" href="pt06.html" title="Part VI. GTK+ Tools">
 <link rel="prev" href="gtk-encode-symbolic-svg.html" title="gtk-encode-symbolic-svg">
 <link rel="next" href="gtk-launch.html" title="gtk-launch">
-<meta name="generator" content="GTK-Doc V1.25.1 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.27 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -111,6 +111,6 @@
 </div>
 </div>
 <div class="footer">
-<hr>Generated by GTK-Doc V1.25.1</div>
+<hr>Generated by GTK-Doc V1.27</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/gtk3/gtk-building.html CHANGED Viewed

@@ -8,7 +8,7 @@
 <link rel="up" href="platform-support.html" title="Part VII. GTK+ Platform Support">
 <link rel="prev" href="platform-support.html" title="Part VII. GTK+ Platform Support">
 <link rel="next" href="gtk-compiling.html" title="Compiling GTK+ Applications">
-<meta name="generator" content="GTK-Doc V1.25.1 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.27 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -468,6 +468,6 @@ How to compile GTK+ itself
 </div>
 </div>
 <div class="footer">
-<hr>Generated by GTK-Doc V1.25.1</div>
+<hr>Generated by GTK-Doc V1.27</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/gtk3/gtk-compiling.html CHANGED Viewed

@@ -8,7 +8,7 @@
 <link rel="up" href="platform-support.html" title="Part VII. GTK+ Platform Support">
 <link rel="prev" href="gtk-building.html" title="Compiling the GTK+ libraries">
 <link rel="next" href="gtk-running.html" title="Running GTK+ Applications">
-<meta name="generator" content="GTK-Doc V1.25.1 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.27 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -67,12 +67,12 @@ Deprecated GTK+ functions are annotated to make the compiler
 emit warnings when they are used (e.g. with gcc, you need to use
 the -Wdeprecated-declarations option). If these warnings are
 problematic, they can be turned off by defining the preprocessor
-symbol <code class="literal">GDK_DISABLE_DEPRECATION_WARNINGS</code> by using the commandline
+symbol <a href="../html/gdk3-General.html#GDK-DISABLE-DEPRECATION-WARNINGS:CAPS"><code class="literal">GDK_DISABLE_DEPRECATION_WARNINGS</code></a> by using the commandline
 option <code class="literal">-DGDK_DISABLE_DEPRECATION_WARNINGS</code>
 </p>
 <p>
 GTK+ deprecation annotations are versioned; by defining the
-macros <a href="../gdk4/gdk4-General.html#GDK-VERSION-MIN-REQUIRED:CAPS"><code class="literal">GDK_VERSION_MIN_REQUIRED</code></a> and <a href="../gdk4/gdk4-General.html#GDK-VERSION-MAX-ALLOWED:CAPS"><code class="literal">GDK_VERSION_MAX_ALLOWED</code></a>,
+macros <a href="../html/gdk3-General.html#GDK-VERSION-MIN-REQUIRED:CAPS"><code class="literal">GDK_VERSION_MIN_REQUIRED</code></a> and <a href="../html/gdk3-General.html#GDK-VERSION-MAX-ALLOWED:CAPS"><code class="literal">GDK_VERSION_MAX_ALLOWED</code></a>,
 you can specify the range of GTK+ versions whose API you want
 to use. APIs that were deprecated before or introduced after
 this range will trigger compiler warnings.
@@ -149,6 +149,6 @@ line option <code class="literal">-DGTK_MULTIDEVICE_SAFE=1</code>.
 </div>
 </div>
 <div class="footer">
-<hr>Generated by GTK-Doc V1.25.1</div>
+<hr>Generated by GTK-Doc V1.27</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/gtk3/gtk-encode-symbolic-svg.html CHANGED Viewed

@@ -8,7 +8,7 @@
 <link rel="up" href="pt06.html" title="Part VI. GTK+ Tools">
 <link rel="prev" href="gtk-update-icon-cache.html" title="gtk-update-icon-cache">
 <link rel="next" href="gtk-builder-tool.html" title="gtk-builder-tool">
-<meta name="generator" content="GTK-Doc V1.25.1 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.27 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -65,6 +65,6 @@
 </div>
 </div>
 <div class="footer">
-<hr>Generated by GTK-Doc V1.25.1</div>
+<hr>Generated by GTK-Doc V1.27</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/gtk3/gtk-getting-started.html CHANGED Viewed

@@ -8,7 +8,7 @@
 <link rel="up" href="gtk.html" title="Part I. GTK+ Overview">
 <link rel="prev" href="gtk.html" title="Part I. GTK+ Overview">
 <link rel="next" href="ch01s02.html" title="Packing">
-<meta name="generator" content="GTK-Doc V1.25.1 (XML mode)">
+<meta name="generator" content="GTK-Doc V1.27 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -134,7 +134,7 @@ main (int    argc,
     is connected to the <code class="function">activate()</code> function above the <code class="function">main()</code> functions.
     The <code class="varname">activate</code> signal will be sent
     when your application is launched with
-    <a href="/home/vagrant/ruby-gnome2.win32/glib2/vendor/local/share/gtk-doc/html/gio/GApplication.html#g-application-run"><code class="function">g_application_run()</code></a> on the line below.
+    <code class="function">g_application_run()</code> on the line below.
     The <code class="function">gtk_application_run()</code> also takes as arguments the pointers to the command line arguments
     counter and string array; this allows GTK+ to parse specific command line
     arguments that control the behavior of GTK+ itself. The parsed arguments
@@ -166,9 +166,9 @@ main (int    argc,
 <p>Finally the window size is set using gtk_window_set_default_size and
     the window is then shown by GTK via <a class="link" href="GtkWidget.html#gtk-widget-show-all" title="gtk_widget_show_all ()"><code class="function">gtk_widget_show_all()</code></a>.</p>
 <p>When you exit the window, by for example pressing the X,
-    the <a href="/home/vagrant/ruby-gnome2.win32/glib2/vendor/local/share/gtk-doc/html/gio/GApplication.html#g-application-run"><code class="function">g_application_run()</code></a> in the main loop returns with a number
+    the <code class="function">g_application_run()</code> in the main loop returns with a number
     which is saved inside an integer named "status". Afterwards, the
-    <a class="link" href="GtkApplication.html" title="GtkApplication"><span class="type">GtkApplication</span></a> object is freed from memory with <a href="/home/vagrant/ruby-gnome2.win32/glib2/vendor/local/share/gtk-doc/html/gobject/gobject-The-Base-Object-Type.html#g-object-unref"><code class="function">g_object_unref()</code></a>.
+    <a class="link" href="GtkApplication.html" title="GtkApplication"><span class="type">GtkApplication</span></a> object is freed from memory with <code class="function">g_object_unref()</code>.
     Finally the status integer is returned and the GTK application exits.</p>
 <p>While the program is running, GTK+ is receiving
     <em class="firstterm">events</em>. These are typically input events caused by
@@ -262,17 +262,17 @@ main (int    argc,
   Using g_signal_connect the button is connected to a function in our app called
   <code class="function">print_hello()</code>, so that when the button is clicked, GTK will call this function.
   As the <code class="function">print_hello()</code> function does not use any data as input, NULL is passed
-  to it. <code class="function">print_hello()</code> calls <a href="/home/vagrant/ruby-gnome2.win32/glib2/vendor/local/share/gtk-doc/html/glib/glib-Warnings-and-Assertions.html#g-print"><code class="function">g_print()</code></a> with the string "Hello World"
+  to it. <code class="function">print_hello()</code> calls <code class="function">g_print()</code> with the string "Hello World"
   which will print Hello World in a terminal if the GTK application was started
   from one.</p>
 <p>After connecting <code class="function">print_hello()</code>, another signal is connected to the "clicked" state
-  of the button using <a href="/home/vagrant/ruby-gnome2.win32/glib2/vendor/local/share/gtk-doc/html/gobject/gobject-Signals.html#g-signal-connect-swapped"><code class="function">g_signal_connect_swapped()</code></a>. This functions is similar to
-  a <a href="/home/vagrant/ruby-gnome2.win32/glib2/vendor/local/share/gtk-doc/html/gobject/gobject-Signals.html#g-signal-connect"><code class="function">g_signal_connect()</code></a> with the difference lying in how the callback function is
-  treated. <a href="/home/vagrant/ruby-gnome2.win32/glib2/vendor/local/share/gtk-doc/html/gobject/gobject-Signals.html#g-signal-connect-swapped"><code class="function">g_signal_connect_swapped()</code></a> allow you to specify what the callback
+  of the button using <code class="function">g_signal_connect_swapped()</code>. This functions is similar to
+  a <code class="function">g_signal_connect()</code> with the difference lying in how the callback function is
+  treated. <code class="function">g_signal_connect_swapped()</code> allow you to specify what the callback
   function should take as parameter by letting you pass it as data. In this case
   the function being called back is <a class="link" href="GtkWidget.html#gtk-widget-destroy" title="gtk_widget_destroy ()"><code class="function">gtk_widget_destroy()</code></a> and the <code class="varname">window</code>
   pointer is passed to it. This has the effect that when the button is clicked,
-  the whole GTK window is destroyed. In contrast if a normal <a href="/home/vagrant/ruby-gnome2.win32/glib2/vendor/local/share/gtk-doc/html/gobject/gobject-Signals.html#g-signal-connect"><code class="function">g_signal_connect()</code></a> were used
+  the whole GTK window is destroyed. In contrast if a normal <code class="function">g_signal_connect()</code> were used
   to connect the "clicked" signal with <a class="link" href="GtkWidget.html#gtk-widget-destroy" title="gtk_widget_destroy ()"><code class="function">gtk_widget_destroy()</code></a>, then the <code class="varname">button</code>
   itself would have been destroyed, not the window.
   More information about creating buttons can be found
@@ -283,6 +283,6 @@ main (int    argc,
   application.</p>
 </div>
 <div class="footer">
-<hr>Generated by GTK-Doc V1.25.1</div>
+<hr>Generated by GTK-Doc V1.27</div>
 </body>
 </html>