From 466b3796bb966eb477fd9e22ed6ae1b582c100af Mon Sep 17 00:00:00 2001
From: Miguel de Icaza <miguel@gnome.org>
Date: Wed, 12 Jan 2005 19:27:37 +0000
Subject: [PATCH] More updates from pixelpapst@users.sourceforge.net

svn path=/trunk/gtk-sharp/; revision=38804
---
 doc/en/Gnome/Druid.xml      | 9 ++++++++-
 doc/en/Gnome/DruidPage.xml  | 8 ++++----
 doc/en/Gtk/CellRenderer.xml | 4 ++--
 doc/en/Gtk/TreeView.xml     | 9 +++++++--
 4 files changed, 21 insertions(+), 9 deletions(-)

diff --git a/doc/en/Gnome/Druid.xml b/doc/en/Gnome/Druid.xml
index 72bff94f9..67c9a6177 100644
--- a/doc/en/Gnome/Druid.xml
+++ b/doc/en/Gnome/Druid.xml
@@ -11,7 +11,14 @@
   <ThreadSafetyStatement>Gtk# is thread aware, but not thread safe; See the <link location="node:gtk-sharp/programming/threads">Gtk# Thread Programming</link> for details.</ThreadSafetyStatement>
   <Docs>
     <summary>Widget for sequentially stepping through some pages.</summary>
-    <remarks>The widget which ultimately holds all of the druid's pages and information. This is the widget which the application developer then places inside an outer widget, such as a dialog box for ultimate display.</remarks>
+    <remarks>
+      <para>
+The druid is a multi-page widget, which lets the developer guide the user through a complex operation by breaking it up into simple steps, showing some helpful text in the process. It is composed of several <see cref="T:Gnome.DruidPage" />s.
+</para>
+      <para>
+The widget which ultimately holds all of the druid's pages and information. This is the widget which the application developer then places inside an outer widget, such as a dialog box for ultimate display.
+</para>
+    </remarks>
   </Docs>
   <Base>
     <BaseTypeName>Gtk.Container</BaseTypeName>
diff --git a/doc/en/Gnome/DruidPage.xml b/doc/en/Gnome/DruidPage.xml
index 618221546..f9f7da774 100644
--- a/doc/en/Gnome/DruidPage.xml
+++ b/doc/en/Gnome/DruidPage.xml
@@ -37,7 +37,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Emit the <see cref="E:Gnome.DruidPage.Finish" /> event.</summary>
+        <summary>Emit the <see cref="E:Gnome.DruidPage.FinishClicked" /> event.</summary>
         <remarks>To be added</remarks>
       </Docs>
     </Member>
@@ -49,7 +49,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Emit the <see cref="E:Gnome.DruidPage.Next" /> event.</summary>
+        <summary>Emit the <see cref="E:Gnome.DruidPage.NextClicked" /> event.</summary>
         <returns>an object of type <see cref="T:System.Boolean" /></returns>
         <remarks>It is called by gnome-druid exclusively. It is expected that non-linear Druids will override this signal and return <see langword="true" /> if it handles changing pages.</remarks>
       </Docs>
@@ -62,7 +62,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Emit the <see cref="E:Gnome.DruidPage.Next" /> event.</summary>
+        <summary>Emit the <see cref="E:Gnome.DruidPage.CancelClicked" /> event.</summary>
         <returns>an object of type <see cref="T:System.Boolean" /></returns>
         <remarks>It is called by gnome-druid exclusively. It is expected that a Druid will override this signal and return <see langword="true" /> if it does not want to exit.</remarks>
       </Docs>
@@ -87,7 +87,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Emit the <see cref="E:Gnome.DruidPage.Back" /> event.</summary>
+        <summary>Emit the <see cref="E:Gnome.DruidPage.BackClicked" /> event.</summary>
         <returns>an object of type <see cref="T:System.Boolean" /></returns>
         <remarks>It is called by <see cref="T:Gnome.Druid" /> exclusively. It is expected that non-linear Druids will override this signal and return <see langword="true" /> if it handles changing pages.</remarks>
       </Docs>
diff --git a/doc/en/Gtk/CellRenderer.xml b/doc/en/Gtk/CellRenderer.xml
index 36e0f6e68..1d07acb62 100644
--- a/doc/en/Gtk/CellRenderer.xml
+++ b/doc/en/Gtk/CellRenderer.xml
@@ -23,7 +23,7 @@
 		To this extent, it is not expected that a <see cref="T:Gtk.CellRenderer" /> keep any permanent state around.
 		Instead, any state is set just prior to use.
 		Then, the cell is measured using <see cref="M:Gtk.CellRendererGetSize(Gtk.Widget,Gdk.Rectangle,System.Int32,System.Int32,System.Int32,System.Int32)" />.
-		Finally, the cell is rendered in the correct location using <see cref="M:Gtk.CellRendererRender(Gdk.Window,Gtk.Widget,Gdk.Rectangle,Gdk.Rectangle,Gdk.Rectangle,Gtk.CellRendererState)" />.
+		Finally, the cell is rendered in the correct location using <see cref="M:Gtk.CellRenderer.Render(Gdk.Window,Gtk.Widget,Gdk.Rectangle,Gdk.Rectangle,Gdk.Rectangle,Gtk.CellRendererState)" />.
 	  </para>
       <para>
 	    There are a number of rules that must be followed when writing a new <see cref="T:Gtk.CellRenderer" />.
@@ -504,4 +504,4 @@
       </Docs>
     </Member>
   </Members>
-</Type>
+</Type>
\ No newline at end of file
diff --git a/doc/en/Gtk/TreeView.xml b/doc/en/Gtk/TreeView.xml
index b64960b68..38fb37baf 100644
--- a/doc/en/Gtk/TreeView.xml
+++ b/doc/en/Gtk/TreeView.xml
@@ -758,7 +758,12 @@ For a example how to handle selection events see <see cref="T:Gtk.TreeSelection"
         <summary>Whether to display alternating, shaded rows in the <see cref="Gtk.TreeView" />.</summary>
         <param name="value">an object of type <see cref="T:System.Boolean" /></param>
         <returns>an object of type <see cref="T:System.Boolean" /></returns>
-        <remarks>Setting <see cref="P:Gtk.TreeView.RulesHint" /> to <see langword="true" /> sets a hint to the theme engine to draw rows in alternating colors.</remarks>
+        <remarks>
+          <para>Setting <see cref="P:Gtk.TreeView.RulesHint" /> to <see langword="true" /> sets a hint to the theme engine to draw rows in alternating colors.</para>
+          <para>
+This property tells GTK# that the user interface for your application requires users to read across tree rows and associate cells with one another. By default, GTK# will then render the tree with alternating row colors. Do not use it just because you prefer the appearance of the ruled tree; that's a question for the theme. Some themes will draw tree rows in alternating colors even when rules are turned off, and users who prefer that appearance all the time can choose those themes. You should set this property only as a semantic hint to the theme engine that your tree makes alternating colors useful from a functional standpoint (since it has lots of columns, generally).
+</para>
+        </remarks>
       </Docs>
     </Member>
     <Member MemberName="EnableSearch">
@@ -1841,4 +1846,4 @@ tree_view.AppendColumn ("title", text, "text", 0);
       </Docs>
     </Member>
   </Members>
-</Type>
+</Type>
\ No newline at end of file