summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-base-nodes.tex
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-base-nodes.tex')
-rw-r--r--Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-base-nodes.tex291
1 files changed, 224 insertions, 67 deletions
diff --git a/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-base-nodes.tex b/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-base-nodes.tex
index 8251a7e96ce..5df4c13b6bb 100644
--- a/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-base-nodes.tex
+++ b/Master/texmf-dist/doc/generic/pgf/text-en/pgfmanual-en-base-nodes.tex
@@ -17,7 +17,7 @@ This section describes the |shapes| module.
\begin{pgfmodule}{shapes}
This module defines commands both for creating nodes and for
creating shapes. The package is loaded automatically by |pgf|, but
- you can load it manually if you have only included |pgfcore|.
+ you can load it manually if you have only included |pgfcore|.
\end{pgfmodule}
@@ -41,7 +41,7 @@ You create a node by calling the macro |\pgfnode| or the more general
|\pgfmultipartnode|. These macro takes several parameters and draws
the requested shape at a certain position. In addition, it will
``remember'' the node's position within the current
-|{pgfpicture}|. You can then, later on, refer to the
+|{pgfpicture}|. You can then, later on, refer to the
node's position. Coordinate transformations are ``fully supported,''
which means that if you used coordinate transformations to shift or
rotate the shape of a node, the node's position will still be correctly
@@ -150,10 +150,11 @@ the description of |\pgfmultipartnode| for more details.
\subsection{Creating Nodes}
-You create a node using one of the following commands:
+
+\subsubsection{Creating Simple Nodes}
\begin{command}{\pgfnode\marg{shape}\marg{anchor}\marg{label
- text}\marg{name}\marg{path usage command}}
+ text}\marg{name}\marg{path usage command}}
This command creates a new node. The \meta{shape} of the node must
have been declared previously using |\pgfdeclareshape|.
@@ -190,7 +191,7 @@ You create a node using one of the following commands:
anchored, but you do not wish the shape itself to the
transformed. In this case, you should call
|\pgftransformresetnontranslations| prior to calling the |\pgfnode|
- command.
+ command.
\begin{codeexample}[]
\begin{tikzpicture}
@@ -212,6 +213,10 @@ You create a node using one of the following commands:
|\pgfmultipartnode| for details.
\end{command}
+
+
+\subsubsection{Creating Multi-Part Nodes}
+
\begin{command}{\pgfmultipartnode\marg{shape}\marg{anchor}\marg{name}\marg{path
usage command}}
This command is the more general (and less user-friendly) version of
@@ -223,7 +228,7 @@ You create a node using one of the following commands:
have setup one \TeX-box. Suppose the shape has two parts: The |text|
part and the |lower| part. Then, prior to calling
|\pgfmultipartnode|, you must have setup the boxes
- |\pgfnodeparttextbox| and |\pgfnodepartlowerbox|. These boxes may
+ |\pgfnodeparttextbox| and |\pgfnodepartlowerbox|. These boxes may
contain any \TeX-text. The shape code will then compute the
positions of the shape's anchors based on the sizes of the these
shapes. Finally, when the node is drawn, the boxes are placed at the
@@ -253,7 +258,7 @@ You create a node using one of the following commands:
exhausting \TeX's limited number of box registers, you can say
\begin{codeexample}[code only]
\newbox\pgfnodepartlowerbox
-\let\pgfnodepartmethodsbox=\pgfnodepartlowerbox
+\let\pgfnodepartmethodsbox=\pgfnodepartlowerbox
\end{codeexample}
Also, when you have a node part name with spaces like |class name|,
it may be useful to create an alias:
@@ -263,12 +268,27 @@ You create a node using one of the following commands:
\end{codeexample}
\end{command}
+\begin{command}{\pgfcoordinate\marg{name}\marg{coordinate}}
+ This command creates a node of shape |coordinate| at the given
+ \meta{coordinate}. Exactly the same effect can be achieved using
+ first a shift of the coordinate system to \meta{coordinate},
+ followed by creating a node of shape |coordinate| named
+ \meta{name}. However, this command is easier and more natural to use
+ and, more importantly, it is much faster.
+\end{command}
+
\begin{command}{\pgfnodealias\marg{new name}\marg{existing node}}
This command does not actually create a new node. Rather, it allows
you to subsequently access the node \meta{existing node} using the
name \meta{new name}.
\end{command}
+
+\begin{command}{\pgfnoderename\marg{new name}\marg{existing node}}
+ This command renames an existing node.
+\end{command}
+
+
There are a number of values that have an influence on the size of a
node. These values are stored in the following keys.
@@ -277,11 +297,11 @@ node. These values are stored in the following keys.
This key stores the \emph{recommended} minimum width of a
shape. Thus, when a shape is drawn and when the shape's width would
be smaller than \meta{dimension}, the shape's width is enlarged by
- adding some empty space.
+ adding some empty space.
Note that this value is just a recommendation. A shape may choose to
ignore this key.
-
+
\begin{codeexample}[]
\begin{tikzpicture}
\draw[help lines] (-2,0) grid (2,1);
@@ -299,7 +319,7 @@ node. These values are stored in the following keys.
\begin{key}{/pgf/minimum size=\meta{dimension}}
\keyalias{tikz}
- This sytle both |/pgf/minimum width| and |/pgf/minimum height| to \meta{dimension}.
+ This style both |/pgf/minimum width| and |/pgf/minimum height| to \meta{dimension}.
\end{key}
@@ -309,7 +329,7 @@ node. These values are stored in the following keys.
inner separation between the label text and the background path. As
before, this value is just a recommendation and a shape may choose
to ignore this key.
-
+
\begin{codeexample}[]
\begin{tikzpicture}
\draw[help lines] (-2,0) grid (2,1);
@@ -337,9 +357,9 @@ node. These values are stored in the following keys.
This key stores the recommended horizontal separation between the
background path and the ``outer anchors.'' For example, if
\meta{dimension} is |1cm| then the |east| anchor will be 1cm to the
- right of the right border of the background path.
+ right of the right border of the background path.
As before, this value is just a recommendation.
-
+
\begin{codeexample}[]
\begin{tikzpicture}
\draw[help lines] (-2,0) grid (2,1);
@@ -368,6 +388,110 @@ node. These values are stored in the following keys.
\end{key}
+\subsubsection{Deferred Node Positioning}
+
+Normally, when a node is created using a command like |\pgfnode|, the
+node is immediately inserted into the current picture. In particular,
+you have no chance to change the position of a created node after it
+has been create. Using |\pgfpositionnodelater| in concert with
+|\pgfpositionnodenow|, you can create a node whose position is
+determined only at some later time.
+
+\begin{command}{\pgfpositionnodelater\marg{macro name}}
+ This command is not a replacement for |\pgfnode|. Rather, when this
+ command is used in a scope, all subsequent node creations in this
+ scope will be affected in the following way: When a node is
+ created, it is not inserted into the current picture. Instead, it
+ is stored in the box |\pgfpositionnodelaterbox|. Furthermore, the
+ node is not relevant for the picture's bounding box, but a bounding
+ box for the node is computed and stored in the macros
+ |\pgfpositionnodelaterminx| to |\pgfpositionnodelatermaxy|. Then,
+ the \meta{macro name} is called with the following macros setup:
+
+ \begin{command}{\pgfpositionnodelaterbox}
+ A box register number (|0| currently) that stores the node's paths
+ and texts. You should move the contents of this box to a box of
+ your choice inside \meta{macro name}.
+ \end{command}
+
+ \begin{command}{\pgfpositionnodelatername}
+ The name of the just-created-node. This name will be the
+ originally "desired" name of the box plus the fixed prefix
+ |not yet positioned@|. The idea is to ensure that the original
+ name is not inadvertently used before the node is actually
+ positioned. When |\pgfpositionnodenow| is called, it will change
+ the name to the original name.
+ \end{command}
+
+ \begin{command}{\pgfpositionnodelaterminx}
+ The minimal $x$-position of a bounding box of the node. This
+ bounding box refers to the node when it is positioned with the
+ anchor at the origin.
+ \end{command}
+ \begin{command}{\pgfpositionnodelaterminy}
+ \end{command}
+ \begin{command}{\pgfpositionnodelatermaxx}
+ \end{command}
+ \begin{command}{\pgfpositionnodelatermaxy}
+ \end{command}
+
+ Once a late node has been created, you can add arbitrary code in the
+ same picture. Then, at some later point, you call
+ |\pgfpositionnodenow| to finally position the node at a given
+ position. At this point, the above macros must have the exact same
+ values they had when \meta{macro name} was called. Note that the
+ above macros are local to a scope that ends right after the call to
+ \meta{macro name}, so it is your job to copy the values to safety
+ inside \meta{macro name}.
+
+ By setting \meta{macro name} to |\relax| (which is the default), you
+ can switch off the whole mechanism. When a picture is interrupted,
+ this is done automatically.
+\end{command}
+
+
+\begin{command}{\pgfpositionnodenow\marg{coordinate}}
+ This command is used to position a node that has previously been
+ created with |\pgfpositionnodelater|. When |\pgfpositionnodenow| is
+ called, the macros and boxes mentioned in the description of
+ |\pgfpositionnodenow| must be set to the value they had when the
+ \meta{macro name} was called. Provided this is the case, this
+ command will insert the box into the current picture, shifted by
+ \meta{coordinate}. Subsequently, you can refer to the node with its
+ original name as if it had just been created.
+
+ \begin{codeexample}[]
+\newbox\mybox
+
+\def\mysaver{
+ \global\setbox\mybox=\box\pgfpositionnodelaterbox
+ \global\let\myname=\pgfpositionnodelatername
+ \global\let\myminx=\pgfpositionnodelaterminx
+ \global\let\myminy=\pgfpositionnodelaterminy
+ \global\let\mymaxx=\pgfpositionnodelatermaxx
+ \global\let\mymaxy=\pgfpositionnodelatermaxy
+}
+
+\begin{tikzpicture}
+ {
+ \pgfpositionnodelater{\mysaver}
+ \node [fill=blue!20,below,rotate=30] (hi) {Hello world};
+ }
+ \draw [help lines] (0,0) grid (3,2);
+
+ \let\pgfpositionnodelatername=\myname
+ \let\pgfpositionnodelaterminx=\myminx
+ \let\pgfpositionnodelaterminy=\myminy
+ \let\pgfpositionnodelatermaxx=\mymaxx
+ \let\pgfpositionnodelatermaxy=\mymaxy
+ \setbox\pgfpositionnodelaterbox=\box\mybox
+ \pgfpositionnodenow{\pgfqpoint{2cm}{2cm}}
+
+ \draw (hi) -- (0,0);
+\end{tikzpicture}
+ \end{codeexample}
+\end{command}
+
\subsection{Using Anchors}
@@ -435,7 +559,7 @@ following commands:
\pgfpointanchor{x}{east}
\xdef\mycoordinate{\noexpand\pgfpoint{\the\pgf@x}{\the\pgf@y}}
}
-
+
\pgfpathcircle{\mycoordinate}{2pt}
\pgfusepath{fill}
\end{pgfpicture}
@@ -453,7 +577,7 @@ following commands:
then |\pgfpointanchor| will return a coordinate that corresponds to
the position of the node's anchor on the page, transformed into the
current coordinate system. For examples and more details see
- Section~\ref{section-cross-pictures-pgf}.
+ Section~\ref{section-cross-pictures-pgf}.
\end{command}
\begin{command}{\pgfpointshapeborder\marg{node}\marg{point}}
@@ -518,7 +642,7 @@ automatically. Rather, you have to proceed as follows:
second run.
\item You have to switch off automatic bounding bound
computations. The reason is that the node in the other picture
- should not influence the size of the bouding box of the current
+ should not influence the size of the bounding box of the current
picture. You should say |\pgfusepath{use as bounding box}| before
using a coordinate in another picture.
\end{enumerate}
@@ -538,7 +662,7 @@ should not attempt to redefine.
\pgfpointanchor{current bounding box}{south east}
\end{codeexample}
returns the lower left corner of the bounding box of the current
- picture.
+ picture.
\end{predefinednode}
\begin{predefinednode}{current path bounding box}
@@ -579,7 +703,7 @@ should not attempt to redefine.
Text absolutely positioned in
the lower left corner.}
}
-\end{pgfpicture}
+\end{pgfpicture}
\end{codeexample}
\end{predefinednode}
@@ -588,7 +712,7 @@ There is also an option that allows you to create new special nodes
quite similar to the above:
\begin{key}{/pgf/local bounding box=\meta{node name}}
\keyalias{tikz}
- This defines a new node \meta{node name} whose size is the bouding
+ This defines a new node \meta{node name} whose size is the bounding
box around all objects in the current scope starting at the position
where this option was given. After the end of the scope, the \meta{node
name} is still available. You can use this option to keep track of
@@ -619,7 +743,7 @@ circumstances) and they need to be constructed reasonably ``fast.''
\pgfname\ must be able to handle pictures with several hundreds of
nodes and documents with thousands of nodes in total. It would not do
if \pgfname\ had to compute and store, say, dozens of anchor positions
-for every node.
+for every node.
\subsubsection{What Must Be Defined For a Shape?}
@@ -630,7 +754,7 @@ In order to define a new shape, you must provide:
a \emph{shape name},
\item
code for computing the \emph{saved anchors} and \emph{saved
- dimensions},
+ dimensions},
\item
code for computing \emph{anchor} positions in terms of the saved anchors,
\item
@@ -648,21 +772,21 @@ In order to define a new shape, you must provide:
Anchors are special places in shape. For example, the |north east|
anchor, which is a normal anchor, lies at the upper right corner of
the |rectangle| shape, as does |\northeast|, which is a saved
-anchor. The difference is the following: \emph{saved anchors are
+anchor. The difference is the following: \emph{saved anchors are
computed and stored for each node, anchors are only computed as
needed.} The user only has access to the normal anchors, but a
normal anchor can just ``copy'' or ``pass through'' the location of a
-saved anchor.
+saved anchor.
The idea behind all this is that a shape can declare a very large
number of normal anchors, but when a node of this shape is created,
these anchors are not actually computed. However, this causes a
problem: When we wish to reference an anchor of a node at some later
-time, we must still able to compute the position of the anchor. For
+time, we must still able to compute the position of the anchor. For
this, we may need a lot of information: What was the transformation
matrix that was in force when the node was created? What was the size
of the text box? What were the values of the different separation
-dimensions? And so on.
+dimensions? And so on.
To solve this problem, \pgfname\ will always compute the locations of
all \emph{saved anchors} and store these positions. Then, when an
@@ -673,17 +797,17 @@ As an example, consider the |rectangle| shape. For this shape two
anchors are saved: The |\northeast| corner and the |\southwest|
corner. A normal anchor like |north west| can now easily be expressed
in terms of these coordinates: Take the $x$-position of the
-|\southwest| point and the $y$-position of the |\northeast| point.
+|\southwest| point and the $y$-position of the |\northeast| point.
The |rectangle| shape currently defines 13 normal anchors, but needs
only two saved anchors. Adding new anchors like a |south south east|
anchor would not increase the memory and computation requirements of
-pictures.
+pictures.
All anchors (both saved and normal) are specified in a local
\emph{shape coordinate space}. This is also true for the background
and foreground paths. The |\pgfnode| macro will automatically apply
appropriate transformations to the coordinates so that the shape is
-shifted to the right anchor or otherwise transformed.
+shifted to the right anchor or otherwise transformed.
\subsubsection{Command for Declaring New Shapes}
@@ -749,12 +873,12 @@ The following command declares a new shape:
The \meta{code} will be executed each time |\pgfnode| (or
|\pgfmultipartnode|) is called to create a node of the shape
- \meta{shape name}. When the \meta{code}
+ \meta{shape name}. When the \meta{code}
is executed, the \TeX-boxes of the node parts will contain the
text labels of the node. Possibly, these box are void. For
example, if there is just a |text| part, the node
|\pgfnodeparttextbox| will be setup when the \meta{code} is
- executed.
+ executed.
The \meta{code} can use the width, height, and depth of the
box(es) to compute the location of the saved anchor. In addition,
@@ -791,7 +915,7 @@ The following command declares a new shape:
origin. Either will be fine, for the final shape this will make no
difference since the shape will be shifted anyway. So, let us
assume that the text label is centered on the origin (this will be
- specified later on using the |text| anchor). We get
+ specified later on using the |text| anchor). We get
the following code for the upper right corner:
\begin{codeexample}[code only]
\savedanchor{\upperrightcorner}{
@@ -802,7 +926,7 @@ The following command declares a new shape:
If we wanted to take, say, the |\pgfshapeminwidth| into account,
we could use the following code:
-
+
\begin{codeexample}[code only]
\savedanchor{\upperrightcorner}{
\pgf@y=.\ht\pgfnodeparttextbox % height of the box
@@ -814,13 +938,13 @@ The following command declares a new shape:
}
\end{codeexample}
Note that we could not have written |.5\pgfshapeminwidth| since
- the minium width is stored in a ``plain text macro,'' not as a
- real dimension. So if |\pgfshapeminwidth| depth were
+ the minimum width is stored in a ``plain text macro,'' not as a
+ real dimension. So if |\pgfshapeminwidth| depth were
2cm, writing |.5\pgfshapeminwidth| would yield the same as |.52cm|.
In the ``real'' |rectangle| shape the code is somewhat more
complex, but you get the basic idea.
- \end{command}
+ \end{command}
\begin{command}{\saveddimen\marg{command}\marg{code}}
This command is similar to |\savedanchor|, only instead of setting
\meta{command} to |\pgfpoint{|$x$|}{|$y$|}|, the \meta{command} is
@@ -828,13 +952,13 @@ The following command declares a new shape:
In the |simple rectangle| shape we might use a saved dimension to
store the depth of the shape box.
-
+
\begin{codeexample}[code only]
\saveddimen{\depth}{
- \pgf@x=\dp\pgfnodeparttextbox
+ \pgf@x=\dp\pgfnodeparttextbox
}
\end{codeexample}
- \end{command}
+ \end{command}
\begin{command}{\savedmacro\marg{command}\marg{code}}
This command is similar to |\saveddimen|, only at some point
in \meta{code}, \meta{command} should be defined appropriately,
@@ -842,11 +966,11 @@ The following command declares a new shape:
In the |regular polygon| shape, a saved macro is used to
store the number of sides of the polygon.
-
+
\begin{codeexample}[code only]
\savedmacro{\sides}{\let\sides\pgfpolygonsides}
\end{codeexample}
- \end{command}
+ \end{command}
\begin{command}{\anchor\marg{name}\marg{code}}
This command declares an anchor named \meta{name}. Unlike for saved
anchors, the \meta{code} will not be executed each time a node is
@@ -870,7 +994,7 @@ The following command declares a new shape:
Let us consider some example for the |simple rectangle|
shape. First, we would like to make the upper right corner
publicly available, for example as |north east|:
-
+
\begin{codeexample}[code only]
\anchor{north east}{\upperrightcorner}
\end{codeexample}
@@ -882,7 +1006,7 @@ The following command declares a new shape:
Next, let us define a |north west| anchor. For this anchor, we can
negate the |\pgf@x| variable:
-
+
\begin{codeexample}[code only]
\anchor{north west}{
\upperrightcorner
@@ -921,18 +1045,51 @@ The following command declares a new shape:
\end{codeexample}
to center the text label on the origin in the shape coordinate
space. Note that we could \emph{not} have written the following:
-
+
\begin{codeexample}[code only]
\anchor{text}{\pgfpoint{-.5\wd\pgfnodeparttextbox}{-.5\ht\pgfnodeparttextbox}}
\end{codeexample}
Do you see why this is wrong? The problem is that the box
|\pgfnodeparttextbox| will most likely not have the correct size
when the anchor is computed. After all, the anchor position might
- be recomputed at a time when several other nodes have been created.
+ be recomputed at a time when several other nodes have been created.
If a shape has several node parts, we would have to define an
- anchor for each part.
- \end{command}
+ anchor for each part.
+ \end{command}
+
+ \begin{command}{\deferredanchor\marg{name}\marg{code}}
+ This command declares an anchor named \meta{name}. It works like
+ |\anchor|. However, unlike for
+ anchors declared by |\anchor|, \meta{name} will \emph{not} be
+ expanded during the shape declaration (i.e.\ not during
+ |\pgfdeclareshape|). Rather, the \meta{name} is expanded when the
+ \emph{node} is actually used (with |\pgfnode| or more likely with
+ |\node|). This may be useful if the anchor name is context
+ dependent (depending, for example, on the value of a key).
+
+\begin{codeexample}[code only]
+\makeatletter
+\def\foo{foo}
+\pgfdeclareshape{simple shape}{%
+ \savedanchor{\center}{%
+ \pgfpointorigin}
+ \anchor{center}{\center}
+ \savedanchor{\anchorfoo}{%
+ \pgf@x=1cm
+ \pgf@y=0cm}
+ \deferredanchor{anchor \foo}{\anchorfoo}}
+
+\begin{tikzpicture}
+ \node[simple shape] (Test1) at (0,0) {};
+ \fill (Test1.anchor foo) circle (2pt) node[below] {anchor foo anchor};
+ %
+ \def\foo{bar}
+ \node[simple shape] (Test2) at (2,2) {};
+ \fill (Test2.anchor bar) circle (2pt) node[below] {anchor bar anchor};
+\end{tikzpicture}
+\end{codeexample}
+ \end{command}
\begin{command}{\anchorborder\marg{code}}
A \emph{border anchor} is an anchor point on the border of the
shape. What exactly is considered as the ``border'' of the shape
@@ -963,7 +1120,7 @@ The following command declares a new shape:
\pgfpointborderrectangle{\pgfpoint{\@tempdima}{\@tempdimb}}{\upperrightcorner}
}
\end{codeexample}
- \end{command}
+ \end{command}
\begin{command}{\backgroundpath\marg{code}}
This command specifies the path that ``makes up'' the background
of the shape. Note that the shape cannot prescribe what is going
@@ -984,17 +1141,17 @@ The following command declares a new shape:
\pgfpathrectanglecorners
{\upperrightcorner}
{\pgfpointscale{-1}{\upperrightcorner}}
-}
+}
\end{codeexample}
As the name suggests, the background path is used ``behind'' the
text labels. Thus, this path is used first, then the text labels are
drawn, possibly obscuring part of the path.
- \end{command}
+ \end{command}
\begin{command}{\foregroundpath\marg{code}}
This command works like |\backgroundpath|, only it is invoked
after the text labels have been drawn. This means that this path can
possibly obscure (part of) the text labels.
- \end{command}
+ \end{command}
\begin{command}{\behindbackgroundpath\marg{code}}
Unlike the previous two commands, \meta{code} should not only
construct a path, it should also use this path in whatever way is
@@ -1006,19 +1163,19 @@ The following command declares a new shape:
path.
Note that the \meta{code} is protected with a |{pgfscope}|.
- \end{command}
+ \end{command}
\begin{command}{\beforebackgroundpath\marg{code}}
This command works like |\behindbackgroundpath|, only the
\meta{code} is executed after the background path has been used,
but before the texts label are drawn.
- \end{command}
+ \end{command}
\begin{command}{\behindforegroundpath\marg{code}}
The \meta{code} is executed after the text labels have been drawn,
but before the foreground path is used.
- \end{command}
+ \end{command}
\begin{command}{\beforeforegroundpath\marg{code}}
This \meta{code} is executed at the very end.
- \end{command}
+ \end{command}
\begin{command}{\inheritsavedanchors|[from=|\marg{another shape name}|]|}
This command allows you to inherit the code for saved anchors from
\meta{another shape name}. The idea is that if you wish to create
@@ -1032,32 +1189,32 @@ The following command declares a new shape:
always have to inherit all saved anchors from another
shape. However, you can inherit the saved anchors of more than one
shape by calling this command several times.
- \end{command}
+ \end{command}
\begin{command}{\inheritbehindbackgroundpath|[from=|\marg{another shape name}|]|}
This command can be used to inherit the code used for the
- drawings behind the background path from \meta{another shape name}.
- \end{command}
+ drawings behind the background path from \meta{another shape name}.
+ \end{command}
\begin{command}{\inheritbackgroundpath|[from=|\marg{another shape name}|]|}
Inherits the background path code from \meta{another shape name}.
- \end{command}
+ \end{command}
\begin{command}{\inheritbeforebackgroundpath|[from=|\marg{another shape name}|]|}
Inherits the before background path code from \meta{another shape name}.
- \end{command}
+ \end{command}
\begin{command}{\inheritbehindforegroundpath|[from=|\marg{another shape name}|]|}
Inherits the behind foreground path code from \meta{another shape name}.
- \end{command}
+ \end{command}
\begin{command}{\inheritforegroundpath|[from=|\marg{another shape name}|]|}
Inherits the foreground path code from \meta{another shape name}.
- \end{command}
+ \end{command}
\begin{command}{\inheritbeforeforegroundpath|[from=|\marg{another shape name}|]|}
Inherits the before foreground path code from \meta{another shape name}.
- \end{command}
+ \end{command}
\begin{command}{\inheritanchor|[from=|\marg{another shape name}|]|\marg{name}}
Inherits the code of one specific anchor named \meta{name} from
\meta{another shape name}. Thus, unlike saved anchors, which must
be inherited collectively, normal anchors can and must be
inherited individually.
- \end{command}
+ \end{command}
\begin{command}{\inheritanchorborder|[from=|\marg{another shape name}|]|}
Inherits the border anchor code from \meta{another shape name}.
\end{command}
@@ -1101,16 +1258,16 @@ The following command declares a new shape:
\node[fill=examplefill,draw,ellipse,double]
at ([shift=(-80:3cm)]x) (y) {Use Case};
- \draw[dashed] (x) -- (y);
+ \draw[dashed] (x) -- (y);
\end{tikzpicture}
\end{codeexample}
-
+
\end{command}
-%%% Local Variables:
+%%% Local Variables:
%%% mode: latex
%%% TeX-master: "pgfmanual"
-%%% End:
+%%% End: