From bb3b34af306aaf2aac9968a5d9665cc9de1d0e36 Mon Sep 17 00:00:00 2001 From: Daniel Boles Date: Thu, 3 Aug 2017 13:14:49 +0100 Subject: [PATCH] Layout: Add GtkFixed to docs as a See_Also --- docs/reference/gtk/tmpl/gtklayout.sgml | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/docs/reference/gtk/tmpl/gtklayout.sgml b/docs/reference/gtk/tmpl/gtklayout.sgml index 0a69839b2f..b9d1f073e3 100644 --- a/docs/reference/gtk/tmpl/gtklayout.sgml +++ b/docs/reference/gtk/tmpl/gtklayout.sgml @@ -7,24 +7,27 @@ Infinite scrollable area containing child widgets and/or custom drawing -#GtkLayout is similar to #GtkDrawingArea in that it's a "blank slate" -and doesn't do anything but paint a blank background by default. It's -different in that it supports scrolling natively (you can add it to a -#GtkScrolledWindow), and it can contain child widgets, since it's a -#GtkContainer. However if you're just going to draw, a #GtkDrawingArea -is a better choice since it has lower overhead. +#GtkLayout is similar to #GtkDrawingArea in that it’s a “blank slate” and +doesn’t do anything except paint a blank background by default. It’s different +in that it supports scrolling natively (you can add it to a #GtkScrolledWindow) +and can contain child widgets since it’s a #GtkContainer. + + + +If you just want to draw, a #GtkDrawingArea is a better choice since it has +lower overhead. If you just need to position child widgets at specific points, +then #GtkFixed provides that functionality on its own. When handling expose events on a #GtkLayout, you must draw to GTK_LAYOUT (layout)->bin_window, rather than to -GTK_WIDGET (layout)->window, as you would for a drawing -area. +GTK_WIDGET (layout)->window, as you would for a #GtkDrawingArea. -#GtkDrawingArea, #GtkScrolledWindow +#GtkDrawingArea, #GtkFixed, #GtkScrolledWindow