[gtk/matthiasc/for-master] doc: Syntax fixes
- From: Matthias Clasen <matthiasc src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gtk/matthiasc/for-master] doc: Syntax fixes
- Date: Tue, 25 May 2021 11:36:02 +0000 (UTC)
commit 4c2761302a95b2176d4786559068b121f70a0d33
Author: Matthias Clasen <mclasen redhat com>
Date: Tue May 25 07:33:55 2021 -0400
doc: Syntax fixes
No, we can't have links that say [constructor@...] or
[mehtod@...] or [methoc@...] or [methos@...] or [metohd@...].
And no, not [signals@...] either.
docs/reference/gtk/migrating-3to4.md | 4 ++--
docs/reference/gtk/question_index.md | 2 +-
gdk/gdkclipboard.c | 2 +-
gdk/gdkframeclock.c | 2 +-
gtk/gtkwidget.c | 4 ++--
5 files changed, 7 insertions(+), 7 deletions(-)
---
diff --git a/docs/reference/gtk/migrating-3to4.md b/docs/reference/gtk/migrating-3to4.md
index 13e5427a3d..a97f9ea8bb 100644
--- a/docs/reference/gtk/migrating-3to4.md
+++ b/docs/reference/gtk/migrating-3to4.md
@@ -279,7 +279,7 @@ holds a reference on them, and GTK holds a reference on toplevel windows.
and cause the whole widget hierarchy to be finalized unless there are other
references that keep widgets alive.
-The [signals@Gtk.Widget::destroy] signal is emitted when a widget is
+The [signal@Gtk.Widget::destroy] signal is emitted when a widget is
disposed, and therefore can no longer be used to break reference cycles.
A typical sign of a reference cycle involving a toplevel window is when
closing the window does not make the application quit.
@@ -571,7 +571,7 @@ for you, so templates work like before.
A few changes to the event controller and [class@Gtk.Gesture] APIs
did not make it back to GTK 3, and have to be taken into account
when moving to GTK 4. One is that the [signal@Gtk.EventControllerMotion::enter]
-and [signals@Gtk.EventControllerMotion::leave] signals have gained new arguments.
+and [signal@Gtk.EventControllerMotion::leave] signals have gained new arguments.
Another is that `GtkGestureMultiPress` has been renamed to [class@Gtk.GestureClick],
and has lost its area property. A [class@Gtk.EventControllerFocus] has been
split off from [class@Gtk.EventControllerKey].
diff --git a/docs/reference/gtk/question_index.md b/docs/reference/gtk/question_index.md
index df053f46c2..656f245ced 100644
--- a/docs/reference/gtk/question_index.md
+++ b/docs/reference/gtk/question_index.md
@@ -544,7 +544,7 @@ the question you have, this list is a good place to start.
No. Most drawing in GTK is not done via cairo anymore (but instead
by the GL or Vulkan renderers of GSK).
- If you use cairo for drawing your own widgets, [mehtod@Gtk.Snapshot.append_cairo]
+ If you use cairo for drawing your own widgets, [method@Gtk.Snapshot.append_cairo]
will choose the most appropriate surface type for you.
If you are interested in using GL for your own drawing, see [class@Gtk.GLArea].
diff --git a/gdk/gdkclipboard.c b/gdk/gdkclipboard.c
index cce1f545f7..5bb58175df 100644
--- a/gdk/gdkclipboard.c
+++ b/gdk/gdkclipboard.c
@@ -905,7 +905,7 @@ gdk_clipboard_read_value_finish (GdkClipboard *clipboard,
* call [method@Gdk.Clipboard.read_texture_finish] to get the result.
*
* This is a simple wrapper around [method@Gdk.Clipboard.read_value_async].
- * Use that function or [methos@Gdk.Clipboard.read_async] directly if you
+ * Use that function or [method@Gdk.Clipboard.read_async] directly if you
* need more control over the operation.
*/
void
diff --git a/gdk/gdkframeclock.c b/gdk/gdkframeclock.c
index 92c9b6fcfc..296230f963 100644
--- a/gdk/gdkframeclock.c
+++ b/gdk/gdkframeclock.c
@@ -51,7 +51,7 @@
* `GdkFrameClock` class for documentation of the phases.
* %GDK_FRAME_CLOCK_PHASE_UPDATE and the [signal@GdkFrameClock::update] signal
* are most interesting for application writers, and are used to update the
- * animations, using the frame time given by [metohd@Gdk.FrameClock.get_frame_time].
+ * animations, using the frame time given by [method@Gdk.FrameClock.get_frame_time].
*
* The frame time is reported in microseconds and generally in the same
* timescale as g_get_monotonic_time(), however, it is not the same
diff --git a/gtk/gtkwidget.c b/gtk/gtkwidget.c
index 10b2ebd745..459aeba2fe 100644
--- a/gtk/gtkwidget.c
+++ b/gtk/gtkwidget.c
@@ -4848,7 +4848,7 @@ gtk_widget_class_set_activate_signal_from_name (GtkWidgetClass *widget_class,
*
* If you wish to handle the activation keybinding yourself, it is
* recommended to use [method@Gtk.WidgetClass.add_shortcut] with an action
- * created with [constructor Gtk SignalAction new].
+ * created with [ctor Gtk SignalAction new].
*
* If @widget isn't activatable, the function returns %FALSE.
*
@@ -11184,7 +11184,7 @@ gtk_widget_class_bind_template_callback_full (GtkWidgetClass *widget_class,
* this class’s template data.
*
* Note that this must be called from a composite widget classes class
- * initializer after calling [methoc@GtkWidgetClass.set_template].
+ * initializer after calling [method@GtkWidgetClass.set_template].
*/
void
gtk_widget_class_set_template_scope (GtkWidgetClass *widget_class,
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]