Commit 8e8d302d authored by Tadej Borovšak's avatar Tadej Borovšak Committed by Javier Jardón

[docs] Move documentation to inline comments: GtkBin

Fixes https://bugzilla.gnome.org/show_bug.cgi?id=612351Signed-off-by: default avatarJavier Jardón <jjardon@gnome.org>
parent 4c0cf046
<!-- ##### SECTION Title ##### -->
GtkBin
<!-- ##### SECTION Short_Description ##### -->
A container with just one child
<!-- ##### SECTION Long_Description ##### -->
<para>
The #GtkBin widget is a container with just one child.
It is not very useful itself, but it is useful for deriving subclasses,
since it provides common code needed for handling a single child widget.
</para>
<para>
Many GTK+ widgets are subclasses of #GtkBin, including #GtkWindow, #GtkButton,
#GtkFrame, #GtkHandleBox, and #GtkScrolledWindow.
</para>
<!-- ##### SECTION See_Also ##### -->
<para>
</para>
<!-- ##### SECTION Stability_Level ##### -->
<!-- ##### STRUCT GtkBin ##### -->
<para>
The #GtkBin-struct struct contains the following fields.
(These fields should be considered read-only. They should never be set by
an application.)
<informaltable pgwide="1" frame="none" role="struct">
<tgroup cols="2"><colspec colwidth="2*"/><colspec colwidth="8*"/>
<tbody>
<row>
<entry>#GtkWidget *child;</entry>
<entry>the child widget.</entry>
</row>
</tbody></tgroup></informaltable>
</para>
<!-- ##### FUNCTION gtk_bin_get_child ##### -->
<para>
</para>
@bin:
@Returns:
......@@ -24,6 +24,19 @@
* GTK+ at ftp://ftp.gtk.org/pub/gtk/.
*/
/**
* SECTION:gtkbin
* @Short_description: A container with just one child
* @Title: GtkBin
*
* The #GtkBin widget is a container with just one child.
* It is not very useful itself, but it is useful for deriving subclasses,
* since it provides common code needed for handling a single child widget.
*
* Many GTK+ widgets are subclasses of #GtkBin, including #GtkWindow,
* #GtkButton, #GtkFrame, #GtkHandleBox or #GtkScrolledWindow.
*/
#include "config.h"
#include "gtkbin.h"
#include "gtkintl.h"
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment