I've done a little experimenting, and have some code that I hope will help you. It's not a complete solution by any means.
It appears that an adviedit
able macro has to be of the form \macro{x=<value>,y=<value>}
for whizzytex
to be able to feed the numbers back in. My first idea was simply to add a style to a \node
so it looked something like \node[advi={x=<value,y=<value>}]
but that didn't seem to work (maybe more experimenting would reveal a way to make this work). So I defined a wrapper around the \node
command which took the coordinates at the start and then handed control over to the original \node
. Because of the way that \node
executes the options it is given (as in \node[draw]
), there's no problem with this.
Here's the code. I'll comment on it in the code.
\documentclass[12pt]{article}
%\url{http://tex.stackexchange.com/q/50468/86}
\usepackage{advi}
\usepackage{tikz}
% We need to use some internal commands with `@`s in them for getting
% the widths of the nodes
\makeatletter
\tikzset{
% This is the workhorse style
advi/.style={
% We do the advi stuff after the node has been placed so that we can
% get access to its width and height. What this means is that our
% node ends up being equivalent to
% \node[at=(x-value,y-value)] {node text} [advi/set advi={x=,y=}];
append after command={[advi/set advi={#1}]},
% As the advi boxes are specified by lower-left corner, we anchor our
% node at the lower-left so that the given coordinate is the node
% coordinate
anchor=south west,
% The parameter #1 is of the form "x=<value>,y=<value>". We trick
% TikZ into taking that as defining some keys in the "/tikz/advi"
% directory
advi/.cd,
#1,
% We use the values that have just been set, namely `/tikz/advi/x`
% and `/tikz/advi/y` to specify the location of the node via the
% `at` key. We need to give the full path as we're currently in at
% `/tikz/advi`
/tikz/at={(\pgfkeysvalueof{/tikz/advi/x},\pgfkeysvalueof{/tikz/advi/y})}
},
% This next bit ensures that the `/tikz/advi/x` and `y` keys can be
% used to store values.
advi/.cd,
x/.initial=0,
y/.initial=0,
% This is the part that specifies the boxes in the dvi. This is
% actually executed after the node has been processed
set advi/.code={
% As the node has been processed, we can get its width and height by
% looking at a couple of anchors.
\tikz@scan@one@point\pgfutil@firstofone(\tikzlastnode.north east)
\pgf@xa=\pgf@x
\pgf@ya=\pgf@y
\tikz@scan@one@point\pgfutil@firstofone(\tikzlastnode.south west)
% We adjust the values to be multiples of `em`s as that's the default
% for advi/whizzytex
\pgfmathsetmacro{\advi@node@w}{(\pgf@xa - \pgf@x)/1em}%
\pgfmathsetmacro{\advi@node@h}{(\pgf@ya - \pgf@y)/1em}%
% Finally, we call the `\adviedit` command
\adviedit{comm=\advinode,w=\advi@node@w,h=\advi@node@h,#1}{}%}
}
}
\makeatother
% This is the command that whizzytex will look for.
\newcommand{\advinode}[1]{%
\node[advi={#1}]
}
\begin{document}
hello world, how are you?
% We use `em` units as those are the defaults for advi/whizzytex.
% Presumably this could be made configurable or some wizardry used
% to ensure that the tikz coordinates and the advi coordinates
% matched.
\begin{tikzpicture}[x=1em,y=1em]
% We can even pass ordinary styles to the node:
\advinode{x=13.6805,y=7.3048}[red,draw] {A};
\advinode{x=5.7699,y=10.5065}[circle,fill=blue!50] {B};
\advinode{x=6.464,y=6.6085} {C};
\advinode{x=7.2497,y=7.8264} {D};
\advinode{x=3.7562,y=6.9931} {E};
\advinode{x=1.8567,y=12.5472} {F};
\advinode{x=9.3650,y=7.0893} {G};
\advinode{x=13.9264,y=4.4529} {H};
\advinode{x=11.4138,y=11.5331} {I};
\advinode{x=3.3900,y=2.6800} {J};
\end{tikzpicture}
\end{document}
I don't trust trying this with the standalone
class, so here's a screenshot instead.
The blue boxes and green lines are those drawn by advi
. Note that they are drawn under the drawing, so are overwritten by the border of the A
node and the filled region of the B
node. They are draggable.
The green lines show that the coordinates are relative to something. Experimenting shows that they are relative to the (0,0)
inside the picture - which is what it should be. (A quick look at the code for advi.sty
shows that there is some interaction with PGF builtin which probably takes care of this bit).
(Lastly, this looks very intriguing and definitely worth learning about.)
I don't really get the question so I hope this is what you wanted. If you include a full document (such that we copy paste and see the problem on our systems) things are much more easier.
Here, you can change the default setting within a scope but your block
style had a node distance
which was resetting every time it is issued. I've made it 2mm such that we can see the difference easier.
\documentclass[tikz]{standalone}
\usetikzlibrary{arrows,shapes.geometric,positioning}
\begin{document}
\begin{tikzpicture}[decision/.style={diamond, draw, text width=4.5em, text badly centered, node distance=3.5cm, inner sep=0pt},
block/.style ={rectangle, draw, text width=6em, text centered, rounded corners, minimum height=4em, minimum height=2em},
cloud/.style ={draw, ellipse, minimum height=2em},
line/.style ={draw,-latex'},
node distance = 1cm,
auto]
\node [block] (1st) {1st};
\node [block, right= of 1st] (2nd1) {2nd1};
\begin{scope}[node distance=2mm and 10mm]%Here we change it for everything inside this scope
\node [block, above= of 2nd1] (2nd2) {2nd2};
\node [block, below= of 2nd1] (2nd3) {2nd3};
\node [block, right= of 2nd1] (3rd1) {3rd1};
\node [block, above= of 3rd1] (3rd2) {3rd2};
\node [block, above= of 3rd2] (3rd3) {3rd3};
\end{scope}
\node [block, below= of 3rd1] (3rd4) {3rd4};
\node [block, below= of 3rd4] (3rd5) {3rd5};
\path [line] (1st) -- (2nd1);
\path [line] (2nd1) -- (2nd2);
\path [line] (2nd1) -- (2nd3);
\path [line] (2nd2) -- (3rd3);
\path [line] (2nd1) -- (3rd1);
\path [line] (1st) -- (2nd1);
\end{tikzpicture}
\end{document}
Best Answer
You can use a
xshift
for the node and use the proper anchor: