aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/fillrule.pngbin0 -> 7404 bytes
-rw-r--r--doc/refman.tex22
2 files changed, 17 insertions, 5 deletions
diff --git a/doc/fillrule.png b/doc/fillrule.png
new file mode 100644
index 0000000..bf84865
--- /dev/null
+++ b/doc/fillrule.png
Binary files differ
diff --git a/doc/refman.tex b/doc/refman.tex
index 8ffa0a9..3be05b5 100644
--- a/doc/refman.tex
+++ b/doc/refman.tex
@@ -207,7 +207,7 @@
\title{Zinc, an advanced scriptable Canvas.\\The 3.4 pre-release Reference Manual.\\\small{[CENA technical Note NT03-532]} }
\author{Patrick Lecoanet, Christophe Mertz}
-\date{18 February 2003}
+\date{25 February 2003}
\begin{document}
@@ -304,7 +304,8 @@ It has been replaced by the GLU library. So TkZinc is again fully free software.
\item TkZinc comes now with a Zinctrace.pm module to trace every TkZinc method call
\item the hierarchical view in ZincDebug.pm can now display some choosen attributes
in a choosen format.
-\item 2 new perl demos in zinc-demos: ``tiger'' and ``curve with bezier control points''
+\item 3 new perl demos in zinc-demos: ``tiger'' and ``curve with bezier control points''
+and ``fillrule''
\item pathTags introduced in 3.2.6 have been documented. Label and label
format documentation has been enhanced.
\end{itemize}
@@ -1597,6 +1598,11 @@ reference) and all list parameters are given as array references.
Returns the \emph{window coordinates} of an item anchor. If no item is named by {\tt tagOrId}
or if the item doesn't support anchors, an error is raised. If more than one item match
{\tt tagOrId}, the topmost in display list order is used.
+\code{
+\# for example to get the lower right corner of a text item\\
+(\$x ,\$y) = \$zinc->anchorxy('myTextTag', 'se');
+}
+
\end{blockindent}
@@ -1730,8 +1736,8 @@ false.
\zinccmd{contour}{tagOrId ?operatorSpec coordListOrTagOrId?}
-{\tt\large \$zinc->{\bf contour}(tagOrId);}\\
-{\tt\large \$zinc->{\bf contour}(tagOrId, operatorAndFlag, coordListOrTagOrId);}
+{\tt\large \$contourNum = \$zinc->{\bf contour}(tagOrId);}\\
+{\tt\large \$contourNum = \$zinc->{\bf contour}(tagOrId, operatorAndFlag, coordListOrTagOrId);}
\begin{blockindent}
Manipulate contours on items that can handle multiples geometric contours. Currently
@@ -1773,6 +1779,8 @@ false.
\item{-1} the list of points is reverted,if needed, so that the points defines
a {\bf clockwise} contour.
\end{description}
+ The exact graphical effect depends on the value of the \attributeref{curve}{fillrule}
+ as described in the \attrtyperef{fillrule} type description.
\item{\ident{remove}} to remove an existing contour
\end{description}
@@ -4010,6 +4018,10 @@ described for example in the chapter 11 of the ``The OpenGL Programming Guide 3r
The Official Guide to Learning OpenGL Version 1.2'', ISBN 0201604582. You can also refer to
the example fillrule provided with TkZinc in \conceptref{zinc-demos}{zinc-demos}. The allowed values are
{\tt odd}, {\tt nonzero}, {\tt positive}, {\tt negative}, and {\tt abs\_geq\_2}.
+The following figure shows the effect of fillrule value on curves with multiple contours:
+
+\fig{fillrule}{Examples of fillrule on curves}{0.4}
+
\end{blockindent}
@@ -4229,7 +4241,7 @@ the example fillrule provided with TkZinc in \conceptref{zinc-demos}{zinc-demos}
Describes the shape of a path connecting two points. The possible values are {\tt
straight}, {\tt rightlightning}, {\tt leftlightning}, {\tt rightcorner}, {\tt
leftcorner}, {\tt doublerightcorner} and {\tt doubleleftcorner}. The following figure
- shows these different line shapes
+ shows these different line shapes:
\fig{alllineshapes}{Examples of all available line shapes}{0.4}