diff options
author | Matt Dew <marcoz@osource.org> | 2011-10-25 21:26:00 -0600 |
---|---|---|
committer | Matt Dew <marcoz@osource.org> | 2011-10-25 21:26:00 -0600 |
commit | 99809f548e74a6b1de67ebcb39da14f9a98a7963 (patch) | |
tree | f436d8e857589fbe90386e30b574e7aa8ee593a2 | |
parent | c299ee07fc33da9f6a08aa39ae7b6dd61f0417b5 (diff) |
proofread CH06.xml
-rw-r--r-- | specs/CH06.xml | 22 |
1 files changed, 16 insertions, 6 deletions
diff --git a/specs/CH06.xml b/specs/CH06.xml index 657df1f..a0a0f23 100644 --- a/specs/CH06.xml +++ b/specs/CH06.xml @@ -87,7 +87,7 @@ see Sections 2.5 and 2.6. </para> <note> -<itemizedlist> +<orderedlist> <listitem> <para> The Intrinsics treatment of stacking requests is deficient in several areas. @@ -106,7 +106,7 @@ Widgets should have resize procedures that can be called more than once without ill effects. </para> </listitem> -</itemizedlist> +</orderedlist> </note> </sect1> @@ -282,7 +282,7 @@ typedef enum { <para> The <emphasis remap='I'>request_mode</emphasis> definitions are from -<function>< X11/X.h >.</function> +<function><X11/X.h>.</function> </para> <informaltable> @@ -367,7 +367,7 @@ structure the caller wants to specify. <para> The <emphasis remap='I'>stack_mode</emphasis> definitions are from -<function>< X11/X.h >:</function> +<function><X11/X.h>:</function> </para> <informaltable> @@ -449,7 +449,7 @@ as an alternative to <funcsynopsis id='XtMakeResizeRequest'> <funcprototype> -<funcdef>XtGeometryResult <function>XtMakeResizeRequest</function></funcdef> +<funcdef>typedef XtGeometryResult <function>XtMakeResizeRequest</function></funcdef> <paramdef>Widget <parameter>w</parameter></paramdef> <paramdef>Dimension <parameter>width</parameter></paramdef> <paramdef>Dimension *<parameter>width_return</parameter></paramdef> @@ -685,6 +685,10 @@ it should return to inform <function>XtMakeGeometryRequest</function> that it does not need to do the configuration itself. +</para> + +<note> +<para> To remain compatible with layout techniques used in older widgets (before <function>XtGeometryDone</function> @@ -699,6 +703,7 @@ resize procedure. A self-contained widget set may choose this alternative geometry management scheme, however, provided that it clearly warns widget developers of the compatibility consequences. </para> +</note> <para> Although @@ -1159,6 +1164,10 @@ replaces it with a pointer to an <function>XtWidgetGeometry</function> structure with <emphasis remap='I'>request_mode</emphasis> equal to zero before calling the query_geometry procedure. +</para> + +<note> +<para> If <function>XtQueryGeometry</function> is called from within a geometry_manager @@ -1171,6 +1180,7 @@ are not guaranteed to be consistent with the requested changes. The change request passed to the geometry manager takes precedence over the preferred geometry. </para> +</note> <para> The query_geometry procedure pointer is of type @@ -1179,7 +1189,7 @@ The query_geometry procedure pointer is of type <funcsynopsis id='_XtGeometryHandler'> <funcprototype> -<funcdef>XtGeometryResult <function>*XtGeometryHandler</function></funcdef> +<funcdef>typedef XtGeometryResult <function>(*XtGeometryHandler)</function></funcdef> <paramdef>Widget <parameter>w</parameter></paramdef> <paramdef>XtWidgetGeometry *<parameter>request</parameter></paramdef> <paramdef>XtWidgetGeometry *<parameter>preferred_return</parameter></paramdef> |