How can I nest multiple groups of nodes with the tikz package? [closed]
For generating nodes with the tikz package, I'd like to nest some. I've tried the environ package to convert the node command into an environment like so:
NewEnviron{NodeEnv}[2]{
node[#1](#2){BODY};
}
This will be used in the following situation where a node containing a new tikzpicture is used:
begin{tikzpicture}
% Adding as many nodes and paths as preferred
% ...
% Adding a level of nesting
begin{NodeEnv}{NodeType}{NodeName}
begin{tikzpicture}
% Adding as many nodes and paths as preferred
% ...
% Adding a level of nesting
begin{NodeEnv}{OtherNodeType}{OtherNodeName}
begin{tikzpicture}
% Etc.
end{tikzpicture}
end{NodeEnv}
end{tikzpicture}
end{NodeEnv}
end{tikzpicture}
As I've understood from some research, is that BODY
will be overwritten by nesting. I've seen something with letxBODYBODY
, but that won't work when I nest the same function. Is there a solution for this? EDIT: This is not the case. BODY is not overwritten and works fine. The 'newenviron' package doesn't work in my case, but the 'environ' package does work.
(As for why I'm nesting tikzpictures: I need to group nodes together and create paths between all those groups of nodes, using the group anchors (by fitting a rectangle around the nodes.))
environments nesting tikz-node
closed as unclear what you're asking by samcarter, JouleV, Raaja, Kurt, Stefan Pinnow Mar 22 at 16:29
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
|
show 2 more comments
For generating nodes with the tikz package, I'd like to nest some. I've tried the environ package to convert the node command into an environment like so:
NewEnviron{NodeEnv}[2]{
node[#1](#2){BODY};
}
This will be used in the following situation where a node containing a new tikzpicture is used:
begin{tikzpicture}
% Adding as many nodes and paths as preferred
% ...
% Adding a level of nesting
begin{NodeEnv}{NodeType}{NodeName}
begin{tikzpicture}
% Adding as many nodes and paths as preferred
% ...
% Adding a level of nesting
begin{NodeEnv}{OtherNodeType}{OtherNodeName}
begin{tikzpicture}
% Etc.
end{tikzpicture}
end{NodeEnv}
end{tikzpicture}
end{NodeEnv}
end{tikzpicture}
As I've understood from some research, is that BODY
will be overwritten by nesting. I've seen something with letxBODYBODY
, but that won't work when I nest the same function. Is there a solution for this? EDIT: This is not the case. BODY is not overwritten and works fine. The 'newenviron' package doesn't work in my case, but the 'environ' package does work.
(As for why I'm nesting tikzpictures: I need to group nodes together and create paths between all those groups of nodes, using the group anchors (by fitting a rectangle around the nodes.))
environments nesting tikz-node
closed as unclear what you're asking by samcarter, JouleV, Raaja, Kurt, Stefan Pinnow Mar 22 at 16:29
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
Welcome to TeX-SE! You should never nesttikzpicture
s. This is not supported. If you describe in more detail what you need, I am pretty sure there will be a solution that does not nesttikzpicture
s, e.g. usingmatrix
,fit
and so on.
– marmot
Mar 19 at 15:45
1
You can put tikzpictures into saveboxes and use usebox inside nodes.
– John Kormylo
Mar 19 at 15:50
@JohnKormylo You should probably add that if you do that you will lose the anchors of the nodes you stored in thesavebox
es.
– marmot
Mar 19 at 16:13
@marmot, if you use [remember picture] in both tikzpictures, you can still use the anchors. OTOH, if you use the same savebox more than once, tikz will get confused.
– John Kormylo
Mar 19 at 16:21
@JohnKormylo No.
– marmot
Mar 19 at 16:36
|
show 2 more comments
For generating nodes with the tikz package, I'd like to nest some. I've tried the environ package to convert the node command into an environment like so:
NewEnviron{NodeEnv}[2]{
node[#1](#2){BODY};
}
This will be used in the following situation where a node containing a new tikzpicture is used:
begin{tikzpicture}
% Adding as many nodes and paths as preferred
% ...
% Adding a level of nesting
begin{NodeEnv}{NodeType}{NodeName}
begin{tikzpicture}
% Adding as many nodes and paths as preferred
% ...
% Adding a level of nesting
begin{NodeEnv}{OtherNodeType}{OtherNodeName}
begin{tikzpicture}
% Etc.
end{tikzpicture}
end{NodeEnv}
end{tikzpicture}
end{NodeEnv}
end{tikzpicture}
As I've understood from some research, is that BODY
will be overwritten by nesting. I've seen something with letxBODYBODY
, but that won't work when I nest the same function. Is there a solution for this? EDIT: This is not the case. BODY is not overwritten and works fine. The 'newenviron' package doesn't work in my case, but the 'environ' package does work.
(As for why I'm nesting tikzpictures: I need to group nodes together and create paths between all those groups of nodes, using the group anchors (by fitting a rectangle around the nodes.))
environments nesting tikz-node
For generating nodes with the tikz package, I'd like to nest some. I've tried the environ package to convert the node command into an environment like so:
NewEnviron{NodeEnv}[2]{
node[#1](#2){BODY};
}
This will be used in the following situation where a node containing a new tikzpicture is used:
begin{tikzpicture}
% Adding as many nodes and paths as preferred
% ...
% Adding a level of nesting
begin{NodeEnv}{NodeType}{NodeName}
begin{tikzpicture}
% Adding as many nodes and paths as preferred
% ...
% Adding a level of nesting
begin{NodeEnv}{OtherNodeType}{OtherNodeName}
begin{tikzpicture}
% Etc.
end{tikzpicture}
end{NodeEnv}
end{tikzpicture}
end{NodeEnv}
end{tikzpicture}
As I've understood from some research, is that BODY
will be overwritten by nesting. I've seen something with letxBODYBODY
, but that won't work when I nest the same function. Is there a solution for this? EDIT: This is not the case. BODY is not overwritten and works fine. The 'newenviron' package doesn't work in my case, but the 'environ' package does work.
(As for why I'm nesting tikzpictures: I need to group nodes together and create paths between all those groups of nodes, using the group anchors (by fitting a rectangle around the nodes.))
environments nesting tikz-node
environments nesting tikz-node
edited Mar 22 at 15:52
David M.
asked Mar 19 at 15:33
David M.David M.
185
185
closed as unclear what you're asking by samcarter, JouleV, Raaja, Kurt, Stefan Pinnow Mar 22 at 16:29
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as unclear what you're asking by samcarter, JouleV, Raaja, Kurt, Stefan Pinnow Mar 22 at 16:29
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
Welcome to TeX-SE! You should never nesttikzpicture
s. This is not supported. If you describe in more detail what you need, I am pretty sure there will be a solution that does not nesttikzpicture
s, e.g. usingmatrix
,fit
and so on.
– marmot
Mar 19 at 15:45
1
You can put tikzpictures into saveboxes and use usebox inside nodes.
– John Kormylo
Mar 19 at 15:50
@JohnKormylo You should probably add that if you do that you will lose the anchors of the nodes you stored in thesavebox
es.
– marmot
Mar 19 at 16:13
@marmot, if you use [remember picture] in both tikzpictures, you can still use the anchors. OTOH, if you use the same savebox more than once, tikz will get confused.
– John Kormylo
Mar 19 at 16:21
@JohnKormylo No.
– marmot
Mar 19 at 16:36
|
show 2 more comments
Welcome to TeX-SE! You should never nesttikzpicture
s. This is not supported. If you describe in more detail what you need, I am pretty sure there will be a solution that does not nesttikzpicture
s, e.g. usingmatrix
,fit
and so on.
– marmot
Mar 19 at 15:45
1
You can put tikzpictures into saveboxes and use usebox inside nodes.
– John Kormylo
Mar 19 at 15:50
@JohnKormylo You should probably add that if you do that you will lose the anchors of the nodes you stored in thesavebox
es.
– marmot
Mar 19 at 16:13
@marmot, if you use [remember picture] in both tikzpictures, you can still use the anchors. OTOH, if you use the same savebox more than once, tikz will get confused.
– John Kormylo
Mar 19 at 16:21
@JohnKormylo No.
– marmot
Mar 19 at 16:36
Welcome to TeX-SE! You should never nest
tikzpicture
s. This is not supported. If you describe in more detail what you need, I am pretty sure there will be a solution that does not nest tikzpicture
s, e.g. using matrix
, fit
and so on.– marmot
Mar 19 at 15:45
Welcome to TeX-SE! You should never nest
tikzpicture
s. This is not supported. If you describe in more detail what you need, I am pretty sure there will be a solution that does not nest tikzpicture
s, e.g. using matrix
, fit
and so on.– marmot
Mar 19 at 15:45
1
1
You can put tikzpictures into saveboxes and use usebox inside nodes.
– John Kormylo
Mar 19 at 15:50
You can put tikzpictures into saveboxes and use usebox inside nodes.
– John Kormylo
Mar 19 at 15:50
@JohnKormylo You should probably add that if you do that you will lose the anchors of the nodes you stored in the
savebox
es.– marmot
Mar 19 at 16:13
@JohnKormylo You should probably add that if you do that you will lose the anchors of the nodes you stored in the
savebox
es.– marmot
Mar 19 at 16:13
@marmot, if you use [remember picture] in both tikzpictures, you can still use the anchors. OTOH, if you use the same savebox more than once, tikz will get confused.
– John Kormylo
Mar 19 at 16:21
@marmot, if you use [remember picture] in both tikzpictures, you can still use the anchors. OTOH, if you use the same savebox more than once, tikz will get confused.
– John Kormylo
Mar 19 at 16:21
@JohnKormylo No.
– marmot
Mar 19 at 16:36
@JohnKormylo No.
– marmot
Mar 19 at 16:36
|
show 2 more comments
1 Answer
1
active
oldest
votes
Not an answer, but a demonstration that you CAN save anchors in saveboxes. Remember to run it twice.
documentclass{standalone}
usepackage{tikz}
newsavebox{tempbox}% reserve global name
begin{document}
saveboxtempbox{begin{tikzpicture}[remember picture]
path (0,0) coordinate (A);% Note: coordinate by itself does NOT affect the bounding box
node (B) at (1,1) {test};
end{tikzpicture}}%
begin{tikzpicture}[remember picture]
node (C) at (0,0) {useboxtempbox};
draw[red] (A) -- (B);
draw[blue] (B.south west) rectangle (B.north east);
draw[green] (C.south west) rectangle (C.north east);
end{tikzpicture}
end{document}
Please try e.g.node[scale=0.5] (C) at (1,0) {useboxtempbox};
in your answer to understand what I meant above. Your example "works" by accident and any nontrivial application will fail, as shown by the .node[scale=0.5] (C) at (1,0) {useboxtempbox};
example.
– marmot
Mar 22 at 17:17
@marmot - I admit that scaling the node does not scale the anchor offsets. I would not be surprised if rotating or any other node operations would cause similar problems. So as Henny Youngman would say, don't do that. One can always apply the transformations INSIDE the savebox.
– John Kormylo
Mar 22 at 17:30
1
Well, the reason why one should avoid nestingtikzpictures
is that the pgf keys of the embedding pictures affect the keys of the inner one. It is true that you can "switch them off" by using asavebox
, as you did. However, then they are "switched off" and you can no longer use any nontrivial transformations and so on. So my take is that "don't do that" applies to the whole story.
– marmot
Mar 22 at 17:35
@marmot - But it is so darn useful! As I said, any transformation you want to apply to the node can be applied inside the savebox, and those work just fine.
– John Kormylo
Mar 22 at 17:52
I guess we disagree on the usefulness. Personally I think this practice leads to shaky results which are in general impossible to control. So far I have not seen anything that can only be achieved by nestingtikzpictures
. However, I have seen many examples where nestingtikzpicture
s lead to problems. Of course, nestingtikzpictures
insavebox
es is fine as long as you do not use their node anchors but just include them in the same way you'd include a graphics.
– marmot
Mar 22 at 17:57
|
show 4 more comments
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Not an answer, but a demonstration that you CAN save anchors in saveboxes. Remember to run it twice.
documentclass{standalone}
usepackage{tikz}
newsavebox{tempbox}% reserve global name
begin{document}
saveboxtempbox{begin{tikzpicture}[remember picture]
path (0,0) coordinate (A);% Note: coordinate by itself does NOT affect the bounding box
node (B) at (1,1) {test};
end{tikzpicture}}%
begin{tikzpicture}[remember picture]
node (C) at (0,0) {useboxtempbox};
draw[red] (A) -- (B);
draw[blue] (B.south west) rectangle (B.north east);
draw[green] (C.south west) rectangle (C.north east);
end{tikzpicture}
end{document}
Please try e.g.node[scale=0.5] (C) at (1,0) {useboxtempbox};
in your answer to understand what I meant above. Your example "works" by accident and any nontrivial application will fail, as shown by the .node[scale=0.5] (C) at (1,0) {useboxtempbox};
example.
– marmot
Mar 22 at 17:17
@marmot - I admit that scaling the node does not scale the anchor offsets. I would not be surprised if rotating or any other node operations would cause similar problems. So as Henny Youngman would say, don't do that. One can always apply the transformations INSIDE the savebox.
– John Kormylo
Mar 22 at 17:30
1
Well, the reason why one should avoid nestingtikzpictures
is that the pgf keys of the embedding pictures affect the keys of the inner one. It is true that you can "switch them off" by using asavebox
, as you did. However, then they are "switched off" and you can no longer use any nontrivial transformations and so on. So my take is that "don't do that" applies to the whole story.
– marmot
Mar 22 at 17:35
@marmot - But it is so darn useful! As I said, any transformation you want to apply to the node can be applied inside the savebox, and those work just fine.
– John Kormylo
Mar 22 at 17:52
I guess we disagree on the usefulness. Personally I think this practice leads to shaky results which are in general impossible to control. So far I have not seen anything that can only be achieved by nestingtikzpictures
. However, I have seen many examples where nestingtikzpicture
s lead to problems. Of course, nestingtikzpictures
insavebox
es is fine as long as you do not use their node anchors but just include them in the same way you'd include a graphics.
– marmot
Mar 22 at 17:57
|
show 4 more comments
Not an answer, but a demonstration that you CAN save anchors in saveboxes. Remember to run it twice.
documentclass{standalone}
usepackage{tikz}
newsavebox{tempbox}% reserve global name
begin{document}
saveboxtempbox{begin{tikzpicture}[remember picture]
path (0,0) coordinate (A);% Note: coordinate by itself does NOT affect the bounding box
node (B) at (1,1) {test};
end{tikzpicture}}%
begin{tikzpicture}[remember picture]
node (C) at (0,0) {useboxtempbox};
draw[red] (A) -- (B);
draw[blue] (B.south west) rectangle (B.north east);
draw[green] (C.south west) rectangle (C.north east);
end{tikzpicture}
end{document}
Please try e.g.node[scale=0.5] (C) at (1,0) {useboxtempbox};
in your answer to understand what I meant above. Your example "works" by accident and any nontrivial application will fail, as shown by the .node[scale=0.5] (C) at (1,0) {useboxtempbox};
example.
– marmot
Mar 22 at 17:17
@marmot - I admit that scaling the node does not scale the anchor offsets. I would not be surprised if rotating or any other node operations would cause similar problems. So as Henny Youngman would say, don't do that. One can always apply the transformations INSIDE the savebox.
– John Kormylo
Mar 22 at 17:30
1
Well, the reason why one should avoid nestingtikzpictures
is that the pgf keys of the embedding pictures affect the keys of the inner one. It is true that you can "switch them off" by using asavebox
, as you did. However, then they are "switched off" and you can no longer use any nontrivial transformations and so on. So my take is that "don't do that" applies to the whole story.
– marmot
Mar 22 at 17:35
@marmot - But it is so darn useful! As I said, any transformation you want to apply to the node can be applied inside the savebox, and those work just fine.
– John Kormylo
Mar 22 at 17:52
I guess we disagree on the usefulness. Personally I think this practice leads to shaky results which are in general impossible to control. So far I have not seen anything that can only be achieved by nestingtikzpictures
. However, I have seen many examples where nestingtikzpicture
s lead to problems. Of course, nestingtikzpictures
insavebox
es is fine as long as you do not use their node anchors but just include them in the same way you'd include a graphics.
– marmot
Mar 22 at 17:57
|
show 4 more comments
Not an answer, but a demonstration that you CAN save anchors in saveboxes. Remember to run it twice.
documentclass{standalone}
usepackage{tikz}
newsavebox{tempbox}% reserve global name
begin{document}
saveboxtempbox{begin{tikzpicture}[remember picture]
path (0,0) coordinate (A);% Note: coordinate by itself does NOT affect the bounding box
node (B) at (1,1) {test};
end{tikzpicture}}%
begin{tikzpicture}[remember picture]
node (C) at (0,0) {useboxtempbox};
draw[red] (A) -- (B);
draw[blue] (B.south west) rectangle (B.north east);
draw[green] (C.south west) rectangle (C.north east);
end{tikzpicture}
end{document}
Not an answer, but a demonstration that you CAN save anchors in saveboxes. Remember to run it twice.
documentclass{standalone}
usepackage{tikz}
newsavebox{tempbox}% reserve global name
begin{document}
saveboxtempbox{begin{tikzpicture}[remember picture]
path (0,0) coordinate (A);% Note: coordinate by itself does NOT affect the bounding box
node (B) at (1,1) {test};
end{tikzpicture}}%
begin{tikzpicture}[remember picture]
node (C) at (0,0) {useboxtempbox};
draw[red] (A) -- (B);
draw[blue] (B.south west) rectangle (B.north east);
draw[green] (C.south west) rectangle (C.north east);
end{tikzpicture}
end{document}
edited Mar 19 at 21:36
answered Mar 19 at 21:17
John KormyloJohn Kormylo
46.1k22672
46.1k22672
Please try e.g.node[scale=0.5] (C) at (1,0) {useboxtempbox};
in your answer to understand what I meant above. Your example "works" by accident and any nontrivial application will fail, as shown by the .node[scale=0.5] (C) at (1,0) {useboxtempbox};
example.
– marmot
Mar 22 at 17:17
@marmot - I admit that scaling the node does not scale the anchor offsets. I would not be surprised if rotating or any other node operations would cause similar problems. So as Henny Youngman would say, don't do that. One can always apply the transformations INSIDE the savebox.
– John Kormylo
Mar 22 at 17:30
1
Well, the reason why one should avoid nestingtikzpictures
is that the pgf keys of the embedding pictures affect the keys of the inner one. It is true that you can "switch them off" by using asavebox
, as you did. However, then they are "switched off" and you can no longer use any nontrivial transformations and so on. So my take is that "don't do that" applies to the whole story.
– marmot
Mar 22 at 17:35
@marmot - But it is so darn useful! As I said, any transformation you want to apply to the node can be applied inside the savebox, and those work just fine.
– John Kormylo
Mar 22 at 17:52
I guess we disagree on the usefulness. Personally I think this practice leads to shaky results which are in general impossible to control. So far I have not seen anything that can only be achieved by nestingtikzpictures
. However, I have seen many examples where nestingtikzpicture
s lead to problems. Of course, nestingtikzpictures
insavebox
es is fine as long as you do not use their node anchors but just include them in the same way you'd include a graphics.
– marmot
Mar 22 at 17:57
|
show 4 more comments
Please try e.g.node[scale=0.5] (C) at (1,0) {useboxtempbox};
in your answer to understand what I meant above. Your example "works" by accident and any nontrivial application will fail, as shown by the .node[scale=0.5] (C) at (1,0) {useboxtempbox};
example.
– marmot
Mar 22 at 17:17
@marmot - I admit that scaling the node does not scale the anchor offsets. I would not be surprised if rotating or any other node operations would cause similar problems. So as Henny Youngman would say, don't do that. One can always apply the transformations INSIDE the savebox.
– John Kormylo
Mar 22 at 17:30
1
Well, the reason why one should avoid nestingtikzpictures
is that the pgf keys of the embedding pictures affect the keys of the inner one. It is true that you can "switch them off" by using asavebox
, as you did. However, then they are "switched off" and you can no longer use any nontrivial transformations and so on. So my take is that "don't do that" applies to the whole story.
– marmot
Mar 22 at 17:35
@marmot - But it is so darn useful! As I said, any transformation you want to apply to the node can be applied inside the savebox, and those work just fine.
– John Kormylo
Mar 22 at 17:52
I guess we disagree on the usefulness. Personally I think this practice leads to shaky results which are in general impossible to control. So far I have not seen anything that can only be achieved by nestingtikzpictures
. However, I have seen many examples where nestingtikzpicture
s lead to problems. Of course, nestingtikzpictures
insavebox
es is fine as long as you do not use their node anchors but just include them in the same way you'd include a graphics.
– marmot
Mar 22 at 17:57
Please try e.g.
node[scale=0.5] (C) at (1,0) {useboxtempbox};
in your answer to understand what I meant above. Your example "works" by accident and any nontrivial application will fail, as shown by the . node[scale=0.5] (C) at (1,0) {useboxtempbox};
example.– marmot
Mar 22 at 17:17
Please try e.g.
node[scale=0.5] (C) at (1,0) {useboxtempbox};
in your answer to understand what I meant above. Your example "works" by accident and any nontrivial application will fail, as shown by the . node[scale=0.5] (C) at (1,0) {useboxtempbox};
example.– marmot
Mar 22 at 17:17
@marmot - I admit that scaling the node does not scale the anchor offsets. I would not be surprised if rotating or any other node operations would cause similar problems. So as Henny Youngman would say, don't do that. One can always apply the transformations INSIDE the savebox.
– John Kormylo
Mar 22 at 17:30
@marmot - I admit that scaling the node does not scale the anchor offsets. I would not be surprised if rotating or any other node operations would cause similar problems. So as Henny Youngman would say, don't do that. One can always apply the transformations INSIDE the savebox.
– John Kormylo
Mar 22 at 17:30
1
1
Well, the reason why one should avoid nesting
tikzpictures
is that the pgf keys of the embedding pictures affect the keys of the inner one. It is true that you can "switch them off" by using a savebox
, as you did. However, then they are "switched off" and you can no longer use any nontrivial transformations and so on. So my take is that "don't do that" applies to the whole story.– marmot
Mar 22 at 17:35
Well, the reason why one should avoid nesting
tikzpictures
is that the pgf keys of the embedding pictures affect the keys of the inner one. It is true that you can "switch them off" by using a savebox
, as you did. However, then they are "switched off" and you can no longer use any nontrivial transformations and so on. So my take is that "don't do that" applies to the whole story.– marmot
Mar 22 at 17:35
@marmot - But it is so darn useful! As I said, any transformation you want to apply to the node can be applied inside the savebox, and those work just fine.
– John Kormylo
Mar 22 at 17:52
@marmot - But it is so darn useful! As I said, any transformation you want to apply to the node can be applied inside the savebox, and those work just fine.
– John Kormylo
Mar 22 at 17:52
I guess we disagree on the usefulness. Personally I think this practice leads to shaky results which are in general impossible to control. So far I have not seen anything that can only be achieved by nesting
tikzpictures
. However, I have seen many examples where nesting tikzpicture
s lead to problems. Of course, nesting tikzpictures
in savebox
es is fine as long as you do not use their node anchors but just include them in the same way you'd include a graphics.– marmot
Mar 22 at 17:57
I guess we disagree on the usefulness. Personally I think this practice leads to shaky results which are in general impossible to control. So far I have not seen anything that can only be achieved by nesting
tikzpictures
. However, I have seen many examples where nesting tikzpicture
s lead to problems. Of course, nesting tikzpictures
in savebox
es is fine as long as you do not use their node anchors but just include them in the same way you'd include a graphics.– marmot
Mar 22 at 17:57
|
show 4 more comments
Welcome to TeX-SE! You should never nest
tikzpicture
s. This is not supported. If you describe in more detail what you need, I am pretty sure there will be a solution that does not nesttikzpicture
s, e.g. usingmatrix
,fit
and so on.– marmot
Mar 19 at 15:45
1
You can put tikzpictures into saveboxes and use usebox inside nodes.
– John Kormylo
Mar 19 at 15:50
@JohnKormylo You should probably add that if you do that you will lose the anchors of the nodes you stored in the
savebox
es.– marmot
Mar 19 at 16:13
@marmot, if you use [remember picture] in both tikzpictures, you can still use the anchors. OTOH, if you use the same savebox more than once, tikz will get confused.
– John Kormylo
Mar 19 at 16:21
@JohnKormylo No.
– marmot
Mar 19 at 16:36