[gtk/docs-fixes: 1/3] docs: Remove redundant SECTION



commit 6ae01f981560a7c5b1f0a65e18ad4d0e88b65e57
Author: Emmanuele Bassi <ebassi gnome org>
Date:   Tue May 12 18:43:56 2020 +0100

    docs: Remove redundant SECTION
    
    We already have a SECTION stanza for gtk-doc.

 gdk/gdktexture.c | 22 +++++-----------------
 1 file changed, 5 insertions(+), 17 deletions(-)
---
diff --git a/gdk/gdktexture.c b/gdk/gdktexture.c
index efbed8ab1ba..3961a57f3a5 100644
--- a/gdk/gdktexture.c
+++ b/gdk/gdktexture.c
@@ -25,7 +25,11 @@
  * It is primarily mean for pixel data that will not change over
  * multiple frames, and will be used for a long time.
  *
- * You cannot get your pixel data back once you've uploaded it.
+ * There are various ways to create #GdkTexture objects from a
+ * #GdkPixbuf, or a Cairo surface, or other pixel data.
+ *
+ * The ownership of the pixel data is transferred to the #GdkTexture
+ * instance; you can only make a copy of it, via gdk_texture_download().
  *
  * #GdkTexture is an immutable object: That means you cannot change
  * anything about it other than increasing the reference count via
@@ -49,22 +53,6 @@ gtk_snapshot_append_texture (GdkSnapshot            *snapshot,
                              GdkTexture             *texture,
                              const graphene_rect_t  *bounds);
 
-/**
- * SECTION:textures
- * @Short_description: Image data for display
- * @Title: GdkTexture
- *
- * A GdkTexture represents image data that can be displayed on screen.
- *
- * There are various ways to create GdkTexture objects from a #GdkPixbuf
- * or a cairo surface, or other pixel data.
- *
- * An important aspect of GdkTextures is that they are immutable - once
- * the image data has been wrapped in a GdkTexture, it may be uploaded
- * to the GPU or used in other ways that make it impractical to allow
- * modification.
- */
-
 /**
  * GdkTexture:
  *


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]