You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
! Package pgf Error: No shape named mynamecurrent subpath start is known.
See the pgf package documentation for explanation.
Type H <return> for immediate help.
...
l.10 \pic (myname) {mypic}
;
The following changes remove the problem:
Using -- instead of controls.
Using (0,0) instead of cycle.
Not naming the picture, i.e., removing myname.
The text was updated successfully, but these errors were encountered:
What I find most interesting is that this works at all. I always thought that the only legal construction that you could use was -- cycle;. Does it work if the pic content is
There were two issues:
1. Pile-up of `name prefix' pgf-tikz#311
There is an extensive and very nice answer on TeX.SX:
https://tex.stackexchange.com/questions/176900
I have now implemented the first suggestion of just overriding
`name prefix'. I still have to test how this interacts with manual
setting of `name prefix', but that doesn't seem to be very common
(at least it doesn't seem to occur in the manual).
2. No resolution of global node names pgf-tikz#717
This had the effect that when requesting `current subpath start' (or
any other global name) from within a pic, the resolution would add
the prefix and suffix with \tikz@pp@name and if the resulting local
name was undefined, throw an error. Now I have implemented a two
step resolution which first checks whether the local name exists and
if it doesn't tries the global name. I hope nobody is relying on
the fact that before global names weren't resolved.
Minimal example:
This raises the following error:
The following changes remove the problem:
--
instead ofcontrols
.(0,0)
instead ofcycle
.myname
.The text was updated successfully, but these errors were encountered: