From d22ff046615bbf7d221f08788d6a50da95686959 Mon Sep 17 00:00:00 2001
From: mertz
Date: Tue, 17 Sep 2002 14:29:52 +0000
Subject: corrections d'erreurs/incompl�tions relev�es par D. Etienne:  -
 $Tk::Zinc::VERSION  - searchCommand pour des groupes atomic

---
 doc/refman.tex | 28 +++++++++++++++++++++-------
 1 file changed, 21 insertions(+), 7 deletions(-)

(limited to 'doc')

diff --git a/doc/refman.tex b/doc/refman.tex
index 6f200aa..aaae473 100644
--- a/doc/refman.tex
+++ b/doc/refman.tex
@@ -478,11 +478,11 @@ The Zinc command creates a new Zinc widget, the general form is
 {\tt\large zinc}\bigskip
 
 {\tt\large \$version = \$mainwindow->zinc();}
-{\tt\large \$Tk::Zinc::version();}
+{\tt\large \$Tk::Zinc::VERSION;}
 
 \end{quotation}
 
-This two expressions can be used to get the version of Zinc. The string returned by the second expression also details the graphic head available. For example : ``zinc-version-3205d X11 GL''.
+These two expressions can be used to get the version of Zinc. The string returned by the second expression also details the graphic head available. For example : ``zinc-version-3205d X11 GL''.
 
 \begin{quotation}
 {\tt\large zinc pathname ?options?}\bigskip
@@ -827,6 +827,14 @@ propagate past it downward. If an item part of an atomic group is under the poin
 will try to trigger bindings associated with the atomic group not with the item under the
 pointer. This improves greatly the metaphor of an indivisible item.
 
+It must also be noted that commands such as \cmdref{find} 'enclosed'/'overlapping' or
+\cmdref{addtag} 'enclosed'/'overlapping' {\tt act differently on an atomic group}.
+Such search command will not traverse an atomic group. So if a part of the atomic
+group is enclosed or overlapping, the search command will return the atomic group
+and not its part.
+
+A small program, \ident{Atomic groups} is available as part of \ident{zinc-demos} to demonstrate the
+atomic groups behaviour.
 
 \section{Display order and display lists}
 
@@ -978,7 +986,7 @@ transformation, \emph{not} to the item transformation itself which is composed \
 taking into account the composition attributes.
 
 As you can see, the transformation process is quite powerful but complex. A small program,
-\ident{tranforms} is available as part of \ident{zinc-demos} to demonstrate the
+\ident{Tranformation testbed} is available as part of \ident{zinc-demos} to demonstrate the
 transformation capabilities of zinc. This is also a great resource to understand how it
 works and to tame its complexity. It is possible to use this program to test one's idea on
 a given transformation problem before coding it as part of a complex application.
@@ -1370,7 +1378,8 @@ reference) and all list parameters are given as array references.
     must be no greater than {\tt xo} and {\tt yo} must be no greater
     than {\tt yc}. All coordinates must be integers. inGroup specifies
     a group to start with instead of the top group and recursive tells
-    if the search should descend in the item tree or not.
+    if the search should descend in the item tree or not. recursive is true
+    by default.
 
     It may be necessary to update the Zinc internal geometry with a call
     to {\tt update} if the current state is not stable (i.e before calling
@@ -1386,7 +1395,8 @@ reference) and all list parameters are given as array references.
     must be no greater than {\tt xo} and {\tt yo} must be no greater than
     {\tt yc}. All coordinates must be integers. inGroup specifies
     a group to start with instead of the top group and recursive tells
-    if the search should descend in the item tree or not.
+    if the search should descend in the item tree or not. recursive is true
+    by default.
 
     See also the {\tt enclosed} variant above for a discussion on updating the geometry.    
 
@@ -1785,8 +1795,12 @@ false.
   For example:\\
   \code{ \# to get the item under the mouse cursor:\\
         \$item = \$zinc->find('withtag', 'current');\\
-        \# to get the closest item of a point:\\ \$closest = \$zinc->find ('closest', \$x, \$y);
+        \# to get the closest item of a point:\\
+        \$closest = \$zinc->find ('closest', \$x, \$y);\\
+        \# to get direct children of an atomic group with a pathtag:\\
+        @children = \$zinc->find('withtag', ''.\$atomicGroup'');
   }
+
   As detailled in \cmdref{addtag} command the following searchCommands are possible:
   \begin{itemize}
         \item{\tt\large
@@ -3751,7 +3765,7 @@ by any new user of Zinc: \attrtyperef{gradient} and \attrtyperef{labelformat}.}
   to its use. Zinc registers a set of bitmaps that can be used for any bitmap valued
   attribute (see \ref{builtinbitmaps}).  Extensions to Tk are available to create or
   manipulate bitmaps from a script. The value may also name a file containing a valid X11
-  bitmap description. The syntax in this cas is {\tt @filename}.
+  bitmap description. The syntax in this case is {\tt @filename}.
 \end{blockindent}
 
 \attrtype{bitmaplist}
-- 
cgit v1.1