A path is a series of straight and curved line segments. It is specified following a \path command and the specification must follow a special syntax, which is described in the subsections of the present section.
This command is available only inside a {tikzpicture} environment.
The <specification> is a long stream of path operations. Most of these path operations tell TikZ how the path is build. For example, when you write --(0,0), you use a line-to operation and it means “continue the path from wherever you are to the origin.”
At any point where TikZ expects a path operation, you can also give some graphic options, which is a list of options in brackets, such as [rounded corners]. These options can have different effects:
|
Another example are the transformation options, which also apply only to subsequent coordinates.
|
|
Most options are of this type. In the above example, we would have had to “split up” the path into several \path commands:
|
By default, the \path command does “nothing” with the path, it just “throws it away.” Thus, if you write \path(0,0)--(1,1);, nothing is drawn in your picture. The only effect is that the area occupied by the picture is (possibly) enlarged so that the path fits inside the area. To actually “do” something with the path, an option like draw or fill must be given somewhere on the path. Commands like \draw do this implicitly.
Finally, it is also possible to give node specifications on a path. Such specifications can come at different locations, but they are always allowed when a normal path operation could follow. A node specification starts with node. Basically, the effect is to typeset the node’s text as normal TEX text and to place it at the “current location” on the path. The details are explained in Section 11.
Note, however, that the nodes are not part of the path in any way. Rather, after everything has been done with the path what is specified by the path options (like filling and drawing the path due to a fill and a draw option somewhere in the <specification>), the nodes are added in a post-processing step.
The following style influences scopes:
|
The perhaps simplest operation is the move-to operation, which is specified by just giving a coordinate where a path operation is expected.
The move-to operation normally starts a path at a certain point. This does not cause a line segment to be created, but it specifies the starting point of the next segment. If a path is already under construction, that is, if several segments have already been created, a move-to operation will start a new part of the path that is not connected to any of the previous segments.
|
In the specification (0,0) --(2,0) (0,1) --(2,1) two move-to operations are specified: (0,0) and (0,1). The other two operations, namely --(2,0) and --(2,1) are line-to operations, described next.
The line-to operation extends the current path from the current point in a straight line to the given coordinate. The “current point” is the endpoint of the previous drawing operation or the point specified by a prior move-to operation.
You use two minus signs followed by a coordinate in round brackets. You can add spaces before and after the --.
When a line-to operation is used and some path segment has just been constructed, for example by another line-to operation, the two line segments become joined. This means that if they are drawn, the point where they meet is “joined” smoothly. To appreciate the difference, consider the following two examples: In the left example, the path consists of two path segments that are not joined, but that happen to share a point, while in the right example a smooth join is shown.
|
Sometimes you want to connect two points via straight lines that are only horizontal and vertical. For this, you can use two path construction operations.
This operation means “first horizontal, then vertical.”
|
This operations means “first vertical, then horizontal.”
The line-to operation can not only be used to append straight lines to the path, but also “snaked” lines (called thus because they look a little bit like snakes seen from above).
TikZ and PGF use a concept that I termed snakes for appending such “squiggly” lines. A snake specifies a way of extending a path between two points in a “fancy manner.”
Normally, a snake will just connect the start point to the end point without starting new subpaths. Thus, a path containing a snaked line can, nevetheless, still be used for filling. However, this is not always the case. Some snakes consist of numerous unconnected segments. “Lines” consisting of such snakes cannot be used as the borders of enclosed areas.
Here are some examples of snakes in action:
|
|
|
No special path operation is needed to use a snake. Instead, you use the following option to “switch on” snaking:
This option has to be given anew for each path. However, you can also leave out the <snake name>. In this case, the enclosing scope’s <snake name> is used. Thus, you can specify a “standard” snake name for scope and then just say \draw[snake] every time this snake should actually be used.
The <snake name>none is special. It can be used to switch off snaking after it has been switched on on a path.
A bit strangely, no valid <snake names> are defined by TikZ by default. Instead, you have to include the library package pgflibrarysnakes. This package defines numerous snakes, see Section 14.2 for the complete list.
Most snakes can be configured. For example, for a snake that looks like a sine curve, you might wish to change the amplitude or the frequency. There are numerous options that influence these parameters. Not all options apply to all snakes, see Section 14.2 once more for details.
|
|
|
|
|
This option can be used with every snake and can be combined with the raise snake option.
|
|
|
|
|
|
|
It is possible to define new snakes, but this cannot be done inside TikZ. You need to use the command \pgfdeclaresnake from the basic level directly, see Section 22.
The following styles define combinations of segment settings that may be useful:
The curve-to operation allows you to extend a path using a Bézier curve.
This operation extends the current path from the current point, let us call it x, via a curve to a the current point y. The curve is a cubic Bézier curve. For such a curve, apart from y, you also specify two control points c and d. The idea is that the curve starts at x, “heading” in the direction of c. Mathematically spoken, the tangent of the curve at x goes through c. Similarly, the curve ends at y, “coming from” the other control point, d. The larger the distance between x and c and between d and y, the larger the curve will be.
If the “and<d>” part is not given, d is assumed to be equal to c.
|
As with the line-to operation, it makes a difference whether two curves are joined because they resulted from consecutive curve-to or line-to operations, or whether they just happen to have the same ending:
|
This operation adds a straight line from the current point to the last point specified by a move-to operation. Note that this need not be the beginning of the path. Furthermore, a smooth join is created between the first segment created after the last move-to operation and the straight line appended by the cycle operation.
Consider the following example. In the left example, two triangles are created using three straight lines, but they are not joined at the ends. In the second example cycle operations are used.
|
A rectangle can obviously be created using four straight lines and a cycle operation. However, since rectangles are needed so often, a special syntax is available for them.
When this operation is used, one corner will be the current point, another corner is given by <corner>, which becomes the new current point.
|
All of the path construction operations mentioned up to now are influenced by the following option:
|
The <inset> describes how big the corner is. Note that the <inset> is not scaled along if you use a scaling option like scale=2.
|
You can switch the rounded corners on and off “in the middle of path” and different corners in the same path can have different corner radii:
|
Here is a rectangle with rounded corners:
|
You should be aware, that there are several pitfalls when using this option. First, the rounded corner will only be an arc (part of a circle) if the angle is 90o. In other cases, the rounded corner will still be round, but “not as nice.”
Second, if there are very short line segments in a path, the “rounding” may cause inadverted effects. In such case it may be necessary to temporarily switch off the rounding using sharp corners.
A circle can be approximated well using four Bézier curves. However, it is difficult to do so correctly. For this reason, a special syntax is available for adding such an approximation of a circle to the current path.
The center of the circle is given by the current point. The new current point of the path will remain to be the center of the circle.
Note that you can add spaces after ellipse, but you have to place spaces around and.
|
The arc operation allows you to add an arc to the current path.
The arc operation adds a part of a circle of the given radius between the given angles. The arc will start at the current point and will end at the end of the arc.
|
|
You can add a grid to the current path using the grid path operation.
This operations adss a grid filling a rectangle whose two corners are given by <corner> and by the previous coordinate. Thus, the typical way in which a grid is drawn is \draw (1,1) grid (3,3);, which yields a grid filling the rectangle whose corners are at (1,1) and (3,3). All coordinate transformations apply to the grid.
|
The stepping of the grid is governed by the following options:
It is important to note that the grid is always “phased” such that it contains the point (0,0) if that point happens to be inside the rectangle. Thus, the grid does not always have an intersection at the corner points; this occurs only if the corner points are multiples of the stepping. Note that due to rounding errors, the “last” lines of a grid may be omitted. In this case, you have to add an epsilon to the corner points.
The following style is useful for drawing grids:
The parabola path operation continues the current path with a parabola. A parabola is a (shifted and scaled) curve defined by the equation f(x) = x2 and looks like this: .
This operation adds a parabola through the current point and the given <coordinate>. If the bend is given, it specifies where the bend should go; the <options> can also be used to specify where the bend is. By default, the bend is at the old current point.
|
The following options influence parabolas:
There is one special property of the <coordinate>: When a relative coordinate is given like +(0,0), the position relative to which this coordinate is “flexible.” More precisely, this position lies somewhere on a line from the old current point to the new current point. The exact position depends on the next option.
The idea is the following: If you say bend pos=0 and bend +(0,0), the bend will be at the old current point. If you say bend pos=1 and bend +(0,0), the bend will be at the new current point. If you say bend pos=0.5 and bend +(0,2cm) the bend will be 2cm above the middle of the line between the start and end point. This is most useful in situations such as the following:
|
In the above example, the bend +(0,2) essentially means “a parabola that is 2cm high” and +(3,0) means “and 3cm wide.” Since this situation arises often, there is a special shortcut option:
|
The following styles are useful shortcuts:
The sin and cos operations are similar to the parabola operation. They, too, can be used to draw (parts of) a sine or cosine curve.
The effect of sin is to draw a scaled and shifted version of a sine curve in the interval [0,/2]. The scaling and shifting is done in such a way that the start of the sine curve in the interval is at the old current point and that the end of the curve in the interval is at <coordinate>. Here is an example that should clarify this:
|
This operation works similarly, only a cosine in the interval [0,/2] is drawn. By correctly alternating sin and cos operations, you can create a complete sine or cosine curve:
|
Note that there is no way to (conveniently) draw an interval on a sine or cosine curve whose end points are not multiples of /2.
The plot operation can be used to append a line or curve to the path that goes through a large number of coordinates. These coordinates are either given in a simple list of coordinates or they are read from some file.
The syntax of the plot comes in different versions.
This operation plots the curve through the coordinates specified in the <further arguments>. The current (sub)path is simply continued, that is, a line-to operation to the first point of the curve is implicitly added. The details of the <further arguments> will be explained in a moment.
This operation plots the curve through the coordinates specified in the <further arguments> by first “moving” to the first coordinate of the curve.
The <further arguments> are used in three different ways to specifying the coordinates of the points to be plotted:
These different ways are explained in the following.
In the first two cases, the points are given directly in the TEX-file as in the following example:
|
Here is an example showing the difference between plot and --plot:
|
The second way of specifying points is to put them in an external file named <filename>. Currently, the only file format that TikZ allows is the following: Each line of the <filename> should contain one line starting with two numbers, separated by a space. Anything following the two numbers on the line is ignored. Also, lines starting with a % or a # are ignored as well as empty lines. (This is exactly the format that GNUPLOT produces when you say set terminal table.) If necessary, more formats will be supported in the future, but it is usually easy to produce a file containing data in this form.
|
The file plots/pgfmanual-sine.table reads:
|
It was produced from the following source, using gnuplot:
|
The <local options> of the plot operation are local to each plot and do not affect other plots “on the same path.” For example, plot[yshift=1cm] will locally shift the plot 1cm upward. Remember, however, that most options can only be applied to paths as a whole. For example, plot[red] does not have the effect of making the plot red. After all, you are trying to “locally” make part of the path red, which is not possible.
Often, you will want to plot points that are given via a function like f(x) = xsinx. Unfortunately, TEX does not really have enough computational power to generate the points on such a function efficiently (it is a text processing program, after all). However, if you allow it, TEX can try to call external programs that can easily produce the necessary points. Currently, TikZ knows how to call GNUPLOT.
When TikZ encounters your operation plot[id=<id>] function{x*sin(x)} for the first time, it will create a file called <prefix><id>.gnuplot, where <prefix> is \jobname. by default, that is, the name of you main .tex file. If no <id> is given, it will be empty, which is alright, but it is better when each plot has a unique <id> for reasons explained in a moment. Next, TikZ writes some initialization code into this file followed by plot x*sin(x). The initialization code sets up things such that the plot operation will write the coordinates into another file called <prefix><id>.table. Finally, this table file is read as if you had said plot file{<prefix><id>.table}.
For the plotting mechanism to work, two conditions must be met:
Unfortunately, these conditions will not always be met. Especially if you pass some source to a coauthor and the coauthor does not have GNUPLOT installed, he or she will have trouble compiling your files.
For this reason, TikZ behaves differently when you compile your graphic for the second time: If upon reaching plot[id=<id>] function{...} the file <prefix><id>.table already exists and if the <prefix><id>.gnuplot file contains what TikZ thinks that it “should” contain, the .table file is immediately read without trying to call a gnuplot program. This approach has the following advantages:
When you use plot function{<gnuplot formula>}, the <gnuplot formula> must be given in the gnuplot syntax, whose details are beyond the scope of this manual. Here is the ultra-condensed essence: Use x as the variable and use the C-syntax for normal plots, use t as the variable for parametric plots. Here are some examples:
|
The following options influence the plot:
|
|
This can be useful for complicated things that need to be passed to GNUPLOT. However, for really complicated situations you should create a special external generating GNUPLOT file and use the file-syntax to include the table “by hand.”
The following styles influence the plot:
|
This is most useful for globally setting a prefix for all plots by saying:
|
As we saw already, it is possible to add marks to a plot using the mark option. When this option is used, a copy of the plot mark is placed on each point of the plot. Note that the marks are placed after the whole path has been drawn/filled/shaded. In this respect, they are handled like text nodes.
In detail, the following options govern how marks are drawn:
One plot mark is special: the ball plot mark is available only it TikZ. The ball color determines the balls’s color. Do not use this option with large number of marks since it will take very long to render in PostScript.
This option is not really necessary, since you achieve the same effect by specifying scale=<factor> as a local option, where <factor> is the quotient of the desired size and the default size. However, using mark size is a bit faster and more natural.
|
There are different things the plot operation can do with the points it reads from a file or from the inlined list of points. By default, it will connect these points by straight lines. However, you can also use options to change the behavior of plot.
|
Note that the smoothing algorithm is not very intelligent. You will get the best results if the bending angles are small, that is, less than about 30o and, even more importantly, if the distances between points are about the same all over the plotting path.
|
|
|
|
|
|
|
When TikZ encounters and opening or a closing brace ({ or }) at some point where a path operation should come, it will open or close a scope. All options that can be applied “locally” will be scoped inside the scope. For example, if you apply a transformation like [xshift=1cm] inside the scoped area, the shifting only applies to the scope. On the other hand, an option like color=red does not have any effect inside a scope since it can only be applied to the path as a whole.
You can add nodes to a path using the node operation. Since this operation is quite complex and since the nodes are not really part of the path itself, there is a separate section dealing with nodes, see Section 11.