Draw arc using relative coordinates with tikz
up vote
3
down vote
favorite
My quetion may be dumb, but consider that I am very new with Tikz.
I am trying to draw a tower similar to Eifel using the following code
documentclass{article}
usepackage{tikz}
usetikzlibrary{shapes.geometric}
usetikzlibrary{shapes.misc}
begin{document}
begin{tikzpicture}[{x=(1mm,0)},{y=(0,1mm)}]
deftowerwd{5} % tower width
deftowerht{10} % tower height
deftowerar{4*towerwd/10} % tower arc radius
deftower#1{% #1=position
draw[thick]
%... tower arc
{#1++(-towerar,0)}
arc(180:0:towerar)--
(towerwd/2,0) to[out=120,in=270]
(0,towerht) to[out=270,in=60]
(-towerwd/2,0)--
cycle
;
}
tower{(0,0)} % this works!
tower{(0,20)} % this is messy!
end{tikzpicture}
end{document}
It works fine when I do tower{(0,0)}
, but becomes messy when I use any other coordinate. What am I doing wrong here?
tikz-pgf
add a comment |
up vote
3
down vote
favorite
My quetion may be dumb, but consider that I am very new with Tikz.
I am trying to draw a tower similar to Eifel using the following code
documentclass{article}
usepackage{tikz}
usetikzlibrary{shapes.geometric}
usetikzlibrary{shapes.misc}
begin{document}
begin{tikzpicture}[{x=(1mm,0)},{y=(0,1mm)}]
deftowerwd{5} % tower width
deftowerht{10} % tower height
deftowerar{4*towerwd/10} % tower arc radius
deftower#1{% #1=position
draw[thick]
%... tower arc
{#1++(-towerar,0)}
arc(180:0:towerar)--
(towerwd/2,0) to[out=120,in=270]
(0,towerht) to[out=270,in=60]
(-towerwd/2,0)--
cycle
;
}
tower{(0,0)} % this works!
tower{(0,20)} % this is messy!
end{tikzpicture}
end{document}
It works fine when I do tower{(0,0)}
, but becomes messy when I use any other coordinate. What am I doing wrong here?
tikz-pgf
1
Welcome to TeX.SX! Can you please expand the code snippet that you have posted to a full minimal working example. It is much easier to help you if we can start with some compilable code that illustrates your problem. A MWE should start with adocumentclass
command, include any necessary packages and be as small as possible to demonstrate your problem. At the moment we have to guess what packages etc you are using before we can compile your code.
– Andrew
Nov 10 at 23:16
Yes, sure! I will edit my question. Thank you, @Andrew
– Brasil
Nov 10 at 23:18
add a comment |
up vote
3
down vote
favorite
up vote
3
down vote
favorite
My quetion may be dumb, but consider that I am very new with Tikz.
I am trying to draw a tower similar to Eifel using the following code
documentclass{article}
usepackage{tikz}
usetikzlibrary{shapes.geometric}
usetikzlibrary{shapes.misc}
begin{document}
begin{tikzpicture}[{x=(1mm,0)},{y=(0,1mm)}]
deftowerwd{5} % tower width
deftowerht{10} % tower height
deftowerar{4*towerwd/10} % tower arc radius
deftower#1{% #1=position
draw[thick]
%... tower arc
{#1++(-towerar,0)}
arc(180:0:towerar)--
(towerwd/2,0) to[out=120,in=270]
(0,towerht) to[out=270,in=60]
(-towerwd/2,0)--
cycle
;
}
tower{(0,0)} % this works!
tower{(0,20)} % this is messy!
end{tikzpicture}
end{document}
It works fine when I do tower{(0,0)}
, but becomes messy when I use any other coordinate. What am I doing wrong here?
tikz-pgf
My quetion may be dumb, but consider that I am very new with Tikz.
I am trying to draw a tower similar to Eifel using the following code
documentclass{article}
usepackage{tikz}
usetikzlibrary{shapes.geometric}
usetikzlibrary{shapes.misc}
begin{document}
begin{tikzpicture}[{x=(1mm,0)},{y=(0,1mm)}]
deftowerwd{5} % tower width
deftowerht{10} % tower height
deftowerar{4*towerwd/10} % tower arc radius
deftower#1{% #1=position
draw[thick]
%... tower arc
{#1++(-towerar,0)}
arc(180:0:towerar)--
(towerwd/2,0) to[out=120,in=270]
(0,towerht) to[out=270,in=60]
(-towerwd/2,0)--
cycle
;
}
tower{(0,0)} % this works!
tower{(0,20)} % this is messy!
end{tikzpicture}
end{document}
It works fine when I do tower{(0,0)}
, but becomes messy when I use any other coordinate. What am I doing wrong here?
tikz-pgf
tikz-pgf
edited Nov 10 at 23:24
asked Nov 10 at 23:14
Brasil
362312
362312
1
Welcome to TeX.SX! Can you please expand the code snippet that you have posted to a full minimal working example. It is much easier to help you if we can start with some compilable code that illustrates your problem. A MWE should start with adocumentclass
command, include any necessary packages and be as small as possible to demonstrate your problem. At the moment we have to guess what packages etc you are using before we can compile your code.
– Andrew
Nov 10 at 23:16
Yes, sure! I will edit my question. Thank you, @Andrew
– Brasil
Nov 10 at 23:18
add a comment |
1
Welcome to TeX.SX! Can you please expand the code snippet that you have posted to a full minimal working example. It is much easier to help you if we can start with some compilable code that illustrates your problem. A MWE should start with adocumentclass
command, include any necessary packages and be as small as possible to demonstrate your problem. At the moment we have to guess what packages etc you are using before we can compile your code.
– Andrew
Nov 10 at 23:16
Yes, sure! I will edit my question. Thank you, @Andrew
– Brasil
Nov 10 at 23:18
1
1
Welcome to TeX.SX! Can you please expand the code snippet that you have posted to a full minimal working example. It is much easier to help you if we can start with some compilable code that illustrates your problem. A MWE should start with a
documentclass
command, include any necessary packages and be as small as possible to demonstrate your problem. At the moment we have to guess what packages etc you are using before we can compile your code.– Andrew
Nov 10 at 23:16
Welcome to TeX.SX! Can you please expand the code snippet that you have posted to a full minimal working example. It is much easier to help you if we can start with some compilable code that illustrates your problem. A MWE should start with a
documentclass
command, include any necessary packages and be as small as possible to demonstrate your problem. At the moment we have to guess what packages etc you are using before we can compile your code.– Andrew
Nov 10 at 23:16
Yes, sure! I will edit my question. Thank you, @Andrew
– Brasil
Nov 10 at 23:18
Yes, sure! I will edit my question. Thank you, @Andrew
– Brasil
Nov 10 at 23:18
add a comment |
1 Answer
1
active
oldest
votes
up vote
4
down vote
accepted
It becomes messy because ++
does not add these coordinates, you might use calc
for that if there was not a (IMHO) much more elegant way: pic
s.
What do pic
s do? A pic is, as its name suggests, a small picture like your tower. pic
s can be placed and transformed. All I did was to move your tower
code inside the definition of a pic
by saying
tikzset{pics/.cd,
tower/.style={code={
draw[thick]
(-towerar,0)
arc(180:0:towerar)--
(towerwd/2,0) to[out=120,in=270]
(0,towerht) to[out=270,in=60]
(-towerwd/2,0)--
cycle
;
}}}
Here, the .cd
switches to the pics
subdirectory of pgfkeys tikz
directory. The rest is just to teach TikZ the tower code.
documentclass{article}
usepackage{tikz}
begin{document}
tikzset{pics/.cd,
tower/.style={code={
draw[thick]
(-towerar,0)
arc(180:0:towerar)--
(towerwd/2,0) to[out=120,in=270]
(0,towerht) to[out=270,in=60]
(-towerwd/2,0)--
cycle
;
}}}
begin{tikzpicture}[{x=(1mm,0)},{y=(0,1mm)}]
deftowerwd{5} % tower width
deftowerht{10} % tower height
deftowerar{4*towerwd/10} % tower arc radius
path (0,0) pic{tower} (0,20) pic{tower};
end{tikzpicture}
end{document}
But this example does not at all explain why people are excited about pics. Rather, you might want to add parameters instead of the somewhat clumsy deftowerwd{5}
and so on statements. And you may want to change parameters from "outside". All this can be done with pic
s.
documentclass{article}
usepackage{tikz}
begin{document}
tikzset{pics/.cd,
tower/.style args={#1 wide and #2 high}{code={
draw[thick]
(-4*#1/10,0)
arc(180:0:4*#1/10)--
(#1/2,0) to[out=120,in=270]
(0,#2) to[out=270,in=60]
(-#1/2,0)--
cycle
;
}}}
begin{tikzpicture}[{x=(1mm,0)},{y=(0,1mm)}]
path (0,0) pic{tower=5 wide and 15 high}
node[below]{Paris} (20,2) pic[rotate=-30,blue]{tower=5 wide and 10 high}
node[below]{Pisa};
end{tikzpicture}
end{document}
Hi, @marmot. Thank you very much for the answer. It works perfectly. Could you please explain the role oftikzset
and its argumentspics/.cd
andtower/.style
? Thank you again.
– Brasil
Nov 11 at 15:21
1
@Brasil I added explanations and a more advanced example.
– marmot
Nov 11 at 15:33
Yeah... sorry. In a hurry, I missed the explanations. Everything is very new for me, so I think I will need to read a bit of external explantions too. Let me a final question: is there any difference if I dotikzset
inside thetikz
environment? Thank you again, @marmot. Its great!
– Brasil
Nov 11 at 15:48
1
@Brasil The answer is: yes and no. No becausetikzset
works, in principle, always the same. Yes because its definitions are not global. In your example you havedeftowerwd{5}
inside thetikzpicture
, sotowerwd
is not known outside because by default definitions are not global. Same thing for pgfkeys: the key value is not known outside thetikzpicture
if you set it inside.
– marmot
Nov 11 at 15:52
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
accepted
It becomes messy because ++
does not add these coordinates, you might use calc
for that if there was not a (IMHO) much more elegant way: pic
s.
What do pic
s do? A pic is, as its name suggests, a small picture like your tower. pic
s can be placed and transformed. All I did was to move your tower
code inside the definition of a pic
by saying
tikzset{pics/.cd,
tower/.style={code={
draw[thick]
(-towerar,0)
arc(180:0:towerar)--
(towerwd/2,0) to[out=120,in=270]
(0,towerht) to[out=270,in=60]
(-towerwd/2,0)--
cycle
;
}}}
Here, the .cd
switches to the pics
subdirectory of pgfkeys tikz
directory. The rest is just to teach TikZ the tower code.
documentclass{article}
usepackage{tikz}
begin{document}
tikzset{pics/.cd,
tower/.style={code={
draw[thick]
(-towerar,0)
arc(180:0:towerar)--
(towerwd/2,0) to[out=120,in=270]
(0,towerht) to[out=270,in=60]
(-towerwd/2,0)--
cycle
;
}}}
begin{tikzpicture}[{x=(1mm,0)},{y=(0,1mm)}]
deftowerwd{5} % tower width
deftowerht{10} % tower height
deftowerar{4*towerwd/10} % tower arc radius
path (0,0) pic{tower} (0,20) pic{tower};
end{tikzpicture}
end{document}
But this example does not at all explain why people are excited about pics. Rather, you might want to add parameters instead of the somewhat clumsy deftowerwd{5}
and so on statements. And you may want to change parameters from "outside". All this can be done with pic
s.
documentclass{article}
usepackage{tikz}
begin{document}
tikzset{pics/.cd,
tower/.style args={#1 wide and #2 high}{code={
draw[thick]
(-4*#1/10,0)
arc(180:0:4*#1/10)--
(#1/2,0) to[out=120,in=270]
(0,#2) to[out=270,in=60]
(-#1/2,0)--
cycle
;
}}}
begin{tikzpicture}[{x=(1mm,0)},{y=(0,1mm)}]
path (0,0) pic{tower=5 wide and 15 high}
node[below]{Paris} (20,2) pic[rotate=-30,blue]{tower=5 wide and 10 high}
node[below]{Pisa};
end{tikzpicture}
end{document}
Hi, @marmot. Thank you very much for the answer. It works perfectly. Could you please explain the role oftikzset
and its argumentspics/.cd
andtower/.style
? Thank you again.
– Brasil
Nov 11 at 15:21
1
@Brasil I added explanations and a more advanced example.
– marmot
Nov 11 at 15:33
Yeah... sorry. In a hurry, I missed the explanations. Everything is very new for me, so I think I will need to read a bit of external explantions too. Let me a final question: is there any difference if I dotikzset
inside thetikz
environment? Thank you again, @marmot. Its great!
– Brasil
Nov 11 at 15:48
1
@Brasil The answer is: yes and no. No becausetikzset
works, in principle, always the same. Yes because its definitions are not global. In your example you havedeftowerwd{5}
inside thetikzpicture
, sotowerwd
is not known outside because by default definitions are not global. Same thing for pgfkeys: the key value is not known outside thetikzpicture
if you set it inside.
– marmot
Nov 11 at 15:52
add a comment |
up vote
4
down vote
accepted
It becomes messy because ++
does not add these coordinates, you might use calc
for that if there was not a (IMHO) much more elegant way: pic
s.
What do pic
s do? A pic is, as its name suggests, a small picture like your tower. pic
s can be placed and transformed. All I did was to move your tower
code inside the definition of a pic
by saying
tikzset{pics/.cd,
tower/.style={code={
draw[thick]
(-towerar,0)
arc(180:0:towerar)--
(towerwd/2,0) to[out=120,in=270]
(0,towerht) to[out=270,in=60]
(-towerwd/2,0)--
cycle
;
}}}
Here, the .cd
switches to the pics
subdirectory of pgfkeys tikz
directory. The rest is just to teach TikZ the tower code.
documentclass{article}
usepackage{tikz}
begin{document}
tikzset{pics/.cd,
tower/.style={code={
draw[thick]
(-towerar,0)
arc(180:0:towerar)--
(towerwd/2,0) to[out=120,in=270]
(0,towerht) to[out=270,in=60]
(-towerwd/2,0)--
cycle
;
}}}
begin{tikzpicture}[{x=(1mm,0)},{y=(0,1mm)}]
deftowerwd{5} % tower width
deftowerht{10} % tower height
deftowerar{4*towerwd/10} % tower arc radius
path (0,0) pic{tower} (0,20) pic{tower};
end{tikzpicture}
end{document}
But this example does not at all explain why people are excited about pics. Rather, you might want to add parameters instead of the somewhat clumsy deftowerwd{5}
and so on statements. And you may want to change parameters from "outside". All this can be done with pic
s.
documentclass{article}
usepackage{tikz}
begin{document}
tikzset{pics/.cd,
tower/.style args={#1 wide and #2 high}{code={
draw[thick]
(-4*#1/10,0)
arc(180:0:4*#1/10)--
(#1/2,0) to[out=120,in=270]
(0,#2) to[out=270,in=60]
(-#1/2,0)--
cycle
;
}}}
begin{tikzpicture}[{x=(1mm,0)},{y=(0,1mm)}]
path (0,0) pic{tower=5 wide and 15 high}
node[below]{Paris} (20,2) pic[rotate=-30,blue]{tower=5 wide and 10 high}
node[below]{Pisa};
end{tikzpicture}
end{document}
Hi, @marmot. Thank you very much for the answer. It works perfectly. Could you please explain the role oftikzset
and its argumentspics/.cd
andtower/.style
? Thank you again.
– Brasil
Nov 11 at 15:21
1
@Brasil I added explanations and a more advanced example.
– marmot
Nov 11 at 15:33
Yeah... sorry. In a hurry, I missed the explanations. Everything is very new for me, so I think I will need to read a bit of external explantions too. Let me a final question: is there any difference if I dotikzset
inside thetikz
environment? Thank you again, @marmot. Its great!
– Brasil
Nov 11 at 15:48
1
@Brasil The answer is: yes and no. No becausetikzset
works, in principle, always the same. Yes because its definitions are not global. In your example you havedeftowerwd{5}
inside thetikzpicture
, sotowerwd
is not known outside because by default definitions are not global. Same thing for pgfkeys: the key value is not known outside thetikzpicture
if you set it inside.
– marmot
Nov 11 at 15:52
add a comment |
up vote
4
down vote
accepted
up vote
4
down vote
accepted
It becomes messy because ++
does not add these coordinates, you might use calc
for that if there was not a (IMHO) much more elegant way: pic
s.
What do pic
s do? A pic is, as its name suggests, a small picture like your tower. pic
s can be placed and transformed. All I did was to move your tower
code inside the definition of a pic
by saying
tikzset{pics/.cd,
tower/.style={code={
draw[thick]
(-towerar,0)
arc(180:0:towerar)--
(towerwd/2,0) to[out=120,in=270]
(0,towerht) to[out=270,in=60]
(-towerwd/2,0)--
cycle
;
}}}
Here, the .cd
switches to the pics
subdirectory of pgfkeys tikz
directory. The rest is just to teach TikZ the tower code.
documentclass{article}
usepackage{tikz}
begin{document}
tikzset{pics/.cd,
tower/.style={code={
draw[thick]
(-towerar,0)
arc(180:0:towerar)--
(towerwd/2,0) to[out=120,in=270]
(0,towerht) to[out=270,in=60]
(-towerwd/2,0)--
cycle
;
}}}
begin{tikzpicture}[{x=(1mm,0)},{y=(0,1mm)}]
deftowerwd{5} % tower width
deftowerht{10} % tower height
deftowerar{4*towerwd/10} % tower arc radius
path (0,0) pic{tower} (0,20) pic{tower};
end{tikzpicture}
end{document}
But this example does not at all explain why people are excited about pics. Rather, you might want to add parameters instead of the somewhat clumsy deftowerwd{5}
and so on statements. And you may want to change parameters from "outside". All this can be done with pic
s.
documentclass{article}
usepackage{tikz}
begin{document}
tikzset{pics/.cd,
tower/.style args={#1 wide and #2 high}{code={
draw[thick]
(-4*#1/10,0)
arc(180:0:4*#1/10)--
(#1/2,0) to[out=120,in=270]
(0,#2) to[out=270,in=60]
(-#1/2,0)--
cycle
;
}}}
begin{tikzpicture}[{x=(1mm,0)},{y=(0,1mm)}]
path (0,0) pic{tower=5 wide and 15 high}
node[below]{Paris} (20,2) pic[rotate=-30,blue]{tower=5 wide and 10 high}
node[below]{Pisa};
end{tikzpicture}
end{document}
It becomes messy because ++
does not add these coordinates, you might use calc
for that if there was not a (IMHO) much more elegant way: pic
s.
What do pic
s do? A pic is, as its name suggests, a small picture like your tower. pic
s can be placed and transformed. All I did was to move your tower
code inside the definition of a pic
by saying
tikzset{pics/.cd,
tower/.style={code={
draw[thick]
(-towerar,0)
arc(180:0:towerar)--
(towerwd/2,0) to[out=120,in=270]
(0,towerht) to[out=270,in=60]
(-towerwd/2,0)--
cycle
;
}}}
Here, the .cd
switches to the pics
subdirectory of pgfkeys tikz
directory. The rest is just to teach TikZ the tower code.
documentclass{article}
usepackage{tikz}
begin{document}
tikzset{pics/.cd,
tower/.style={code={
draw[thick]
(-towerar,0)
arc(180:0:towerar)--
(towerwd/2,0) to[out=120,in=270]
(0,towerht) to[out=270,in=60]
(-towerwd/2,0)--
cycle
;
}}}
begin{tikzpicture}[{x=(1mm,0)},{y=(0,1mm)}]
deftowerwd{5} % tower width
deftowerht{10} % tower height
deftowerar{4*towerwd/10} % tower arc radius
path (0,0) pic{tower} (0,20) pic{tower};
end{tikzpicture}
end{document}
But this example does not at all explain why people are excited about pics. Rather, you might want to add parameters instead of the somewhat clumsy deftowerwd{5}
and so on statements. And you may want to change parameters from "outside". All this can be done with pic
s.
documentclass{article}
usepackage{tikz}
begin{document}
tikzset{pics/.cd,
tower/.style args={#1 wide and #2 high}{code={
draw[thick]
(-4*#1/10,0)
arc(180:0:4*#1/10)--
(#1/2,0) to[out=120,in=270]
(0,#2) to[out=270,in=60]
(-#1/2,0)--
cycle
;
}}}
begin{tikzpicture}[{x=(1mm,0)},{y=(0,1mm)}]
path (0,0) pic{tower=5 wide and 15 high}
node[below]{Paris} (20,2) pic[rotate=-30,blue]{tower=5 wide and 10 high}
node[below]{Pisa};
end{tikzpicture}
end{document}
edited Nov 11 at 15:33
answered Nov 10 at 23:36
marmot
77.7k487166
77.7k487166
Hi, @marmot. Thank you very much for the answer. It works perfectly. Could you please explain the role oftikzset
and its argumentspics/.cd
andtower/.style
? Thank you again.
– Brasil
Nov 11 at 15:21
1
@Brasil I added explanations and a more advanced example.
– marmot
Nov 11 at 15:33
Yeah... sorry. In a hurry, I missed the explanations. Everything is very new for me, so I think I will need to read a bit of external explantions too. Let me a final question: is there any difference if I dotikzset
inside thetikz
environment? Thank you again, @marmot. Its great!
– Brasil
Nov 11 at 15:48
1
@Brasil The answer is: yes and no. No becausetikzset
works, in principle, always the same. Yes because its definitions are not global. In your example you havedeftowerwd{5}
inside thetikzpicture
, sotowerwd
is not known outside because by default definitions are not global. Same thing for pgfkeys: the key value is not known outside thetikzpicture
if you set it inside.
– marmot
Nov 11 at 15:52
add a comment |
Hi, @marmot. Thank you very much for the answer. It works perfectly. Could you please explain the role oftikzset
and its argumentspics/.cd
andtower/.style
? Thank you again.
– Brasil
Nov 11 at 15:21
1
@Brasil I added explanations and a more advanced example.
– marmot
Nov 11 at 15:33
Yeah... sorry. In a hurry, I missed the explanations. Everything is very new for me, so I think I will need to read a bit of external explantions too. Let me a final question: is there any difference if I dotikzset
inside thetikz
environment? Thank you again, @marmot. Its great!
– Brasil
Nov 11 at 15:48
1
@Brasil The answer is: yes and no. No becausetikzset
works, in principle, always the same. Yes because its definitions are not global. In your example you havedeftowerwd{5}
inside thetikzpicture
, sotowerwd
is not known outside because by default definitions are not global. Same thing for pgfkeys: the key value is not known outside thetikzpicture
if you set it inside.
– marmot
Nov 11 at 15:52
Hi, @marmot. Thank you very much for the answer. It works perfectly. Could you please explain the role of
tikzset
and its arguments pics/.cd
and tower/.style
? Thank you again.– Brasil
Nov 11 at 15:21
Hi, @marmot. Thank you very much for the answer. It works perfectly. Could you please explain the role of
tikzset
and its arguments pics/.cd
and tower/.style
? Thank you again.– Brasil
Nov 11 at 15:21
1
1
@Brasil I added explanations and a more advanced example.
– marmot
Nov 11 at 15:33
@Brasil I added explanations and a more advanced example.
– marmot
Nov 11 at 15:33
Yeah... sorry. In a hurry, I missed the explanations. Everything is very new for me, so I think I will need to read a bit of external explantions too. Let me a final question: is there any difference if I do
tikzset
inside the tikz
environment? Thank you again, @marmot. Its great!– Brasil
Nov 11 at 15:48
Yeah... sorry. In a hurry, I missed the explanations. Everything is very new for me, so I think I will need to read a bit of external explantions too. Let me a final question: is there any difference if I do
tikzset
inside the tikz
environment? Thank you again, @marmot. Its great!– Brasil
Nov 11 at 15:48
1
1
@Brasil The answer is: yes and no. No because
tikzset
works, in principle, always the same. Yes because its definitions are not global. In your example you have deftowerwd{5}
inside the tikzpicture
, so towerwd
is not known outside because by default definitions are not global. Same thing for pgfkeys: the key value is not known outside the tikzpicture
if you set it inside.– marmot
Nov 11 at 15:52
@Brasil The answer is: yes and no. No because
tikzset
works, in principle, always the same. Yes because its definitions are not global. In your example you have deftowerwd{5}
inside the tikzpicture
, so towerwd
is not known outside because by default definitions are not global. Same thing for pgfkeys: the key value is not known outside the tikzpicture
if you set it inside.– marmot
Nov 11 at 15:52
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f459391%2fdraw-arc-using-relative-coordinates-with-tikz%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Welcome to TeX.SX! Can you please expand the code snippet that you have posted to a full minimal working example. It is much easier to help you if we can start with some compilable code that illustrates your problem. A MWE should start with a
documentclass
command, include any necessary packages and be as small as possible to demonstrate your problem. At the moment we have to guess what packages etc you are using before we can compile your code.– Andrew
Nov 10 at 23:16
Yes, sure! I will edit my question. Thank you, @Andrew
– Brasil
Nov 10 at 23:18