Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

tikz, callouts pointers

544 views
Skip to first unread message

Zarko F. Cucej

unread,
Oct 31, 2010, 6:20:04 PM10/31/10
to
Hi,
please consider the following example:

\documentclass{article}
%---------------------------------------------------------------%
\usepackage{tikz}
\usetikzlibrary{%
shapes.callouts,%
}
\begin{document}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{tikzpicture}[>=stealth,
remark/.style = {shape=rectangle callout, rounded corners=1pt,
draw=blue!50, thin, fill=blue!10,
inner sep=2pt, text width=11ex, align=center,
font=\footnotesize},
]\sffamily
\node[name=test,inner sep=2mm,draw] {TEST};
\node[remark,%
callout absolute pointer={(test.south)},%
below left=7mm] at (test.south) {explanation of the test};
\end{tikzpicture}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\end{document}

compiling this example I receive error:

! Undefined control sequence.
\pgf@sh@bg@rectangle callout ...f@sh@np@\pgf@test
\noexpand \endcsname
}\ede...
l.27 ...at (test.south) {explanation of the test};

?


with hit of "enter" key latex generate picture almost as I expected (the
text in callout shape is not in center of shape, but this now is not
very important to me).

I test this with recent CVS of TikZ as well with TikZ 2.1. If I coment
line with callout pointer, then there is no error, but the picture is
wrong. This test work as expected about half year ago with this time CVS
version of the TikZ, so is it with last version of TikZ introduced some
bug or I doing something wrong?

Please, help me.

Regards, Zarko

Marc van Dongen

unread,
Nov 1, 2010, 3:10:49 AM11/1/10
to

Hi,

The example is not exactly minimal. I get the same with the following.

\documentclass{article}
%---------------------------------------------------------------%
\usepackage{tikz}
\usetikzlibrary{%
shapes.callouts,%
}
\begin{document}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{tikzpicture}

\node[rectangle callout,%
callout absolute pointer={(0,0)}] (0,0) {explanation of


the test};
\end{tikzpicture}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\end{document}

As far as I can tell this should be ok. Removing the `callout absolute
pointer={(0,0)' solves the problem. Again, I don't see anything wrong
with it.

As a test, I tried to compile a document of mine which also uses
callouts. I get the same error as you. I recently compiled this
document with a CVS version of pgf and this was OK. However, since
then I installed the most recent pgf from CTAN.

It looks like a bug to me.

Regards,


Marc van Dongen

vibrovski

unread,
Nov 1, 2010, 3:31:17 AM11/1/10
to

Hi,

I believe pgfmoduleshapes.code.tex was updated at the beginning of
September changing \pgf@test to \pgf@node@name. This change has not
been updated in the callout code. Changing \pgf@test to
\pgf@node@name *should* fix it.

Regards

Mark

Marc van Dongen

unread,
Nov 1, 2010, 3:44:33 AM11/1/10
to
On Nov 1, 7:31 am, vibrovski <vibrov...@googlemail.com> wrote:

Hi Mark,

> I believe  pgfmoduleshapes.code.tex was updated at the beginning of
> September changing \pgf@test to \pgf@node@name. This change has not
> been updated in the callout code. Changing  \pgf@test to
> \pgf@node@name *should* fix it.

I looked for \pgf@test in pgfmoduleshapes.code.tex but I couldn't find
it. However, there do seem to be some other files that depend on it:

$ find /usr/local/texlive/2010/texmf/base/tex/generic/pgf -name
\*.tex -exec grep -w -l pgf@test {} \;
/usr/local/texlive/2010/texmf/base/tex/generic/pgf/basiclayer/
pgfcorelayers.code.tex
/usr/local/texlive/2010/texmf/base/tex/generic/pgf/basiclayer/
pgfcorepathprocessing.code.tex
/usr/local/texlive/2010/texmf/base/tex/generic/pgf/frontendlayer/tikz/
libraries/graphs/tikzlibrarygraphs.code.tex
/usr/local/texlive/2010/texmf/base/tex/generic/pgf/libraries/shapes/
pgflibraryshapes.callouts.code.tex
/usr/local/texlive/2010/texmf/base/tex/generic/pgf/libraries/
decorations/pgflibrarydecorations.text.code.tex

Regards,


Marc van Dongen

vibrovski

unread,
Nov 1, 2010, 4:44:09 AM11/1/10
to

Hi,

You won't find \pgf@test in pgfmoduleshapes.code.tex because at the
beginning of September
instances of \pgf@test in pgfmoduleshapes.code.tex were changed to
\pgf@node@name (which I think is what I said).

Changing the instances of \pgf@test in the callout code to
\pgf@node@name *should* fix the issue.

Regards

Mark

Marc van Dongen

unread,
Nov 1, 2010, 4:49:54 AM11/1/10
to
On Nov 1, 8:44 am, vibrovski <vibrov...@googlemail.com> wrote:

> You won't find \pgf@test in pgfmoduleshapes.code.tex because at the
> beginning of September
> instances of \pgf@test in pgfmoduleshapes.code.tex were changed to
> \pgf@node@name (which I think is what I said).
>
> Changing the instances of \pgf@test in the callout code to
> \pgf@node@name  *should* fix the issue.
>
> Regards
>
> Mark

OK. I misread. Are these all the modules which I located with find?

Regards,


Marc van Dongen

vibrovski

unread,
Nov 1, 2010, 5:38:43 AM11/1/10
to

Hi,

Just pgflibraryshapes.callouts.code.tex should need to be changed to
fix the OP's problem.

Changing the other files will result in disaster. Or at least a
multitude of errors.

Regards

mark

Marc van Dongen

unread,
Nov 1, 2010, 5:54:12 AM11/1/10
to
On Nov 1, 9:38 am, vibrovski <vibrov...@googlemail.com> wrote:
> On Nov 1, 8:49 am, Marc van Dongen <don...@cs.ucc.ie> wrote:
>
>

> Hi,
>
> Just pgflibraryshapes.callouts.code.tex  should need to be changed to
> fix the OP's problem.

Hi Mark,


Thanks. That worked.

Regards,


Marc van Dongen

Zarko F. Cucej

unread,
Nov 1, 2010, 6:53:21 AM11/1/10
to

[...]


> Hi,
>
> I believe pgfmoduleshapes.code.tex was updated at the beginning of
> September changing \pgf@test to \pgf@node@name. This change has not
> been updated in the callout code. Changing \pgf@test to
> \pgf@node@name *should* fix it.
>
> Regards
>
> Mark

Dear Mark,
this solve my problem. Thank you very much!

Best regards, Zarko

Zarko F. Cucej

unread,
Nov 1, 2010, 7:03:15 AM11/1/10
to

Dear Marc van Dogen,
thank you for checking my problem and confirm my suspect, that there
should be a bug.

The example really is not minimal (well I didn't claim this), but I was
hoping that it is enough handy to see my problem. With Mark solution I
get all may pictures with call outs back! And the minor problem with
text centering also disappear.

Thank you very much again. Regards, Zarko

Christophe Jorssen

unread,
Nov 1, 2010, 5:36:21 PM11/1/10
to
On Mon, 01 Nov 2010 02:38:43 -0700, vibrovski wrote:
>
> Just pgflibraryshapes.callouts.code.tex should need to be changed to
> fix the OP's problem.
>
> Changing the other files will result in disaster. Or at least a
> multitude of errors.

Changed in the cvs repo.

Thanks for the report and for the fix.

--
Christophe

Vitaly Repin

unread,
Nov 1, 2013, 5:49:08 PM11/1/13
to
Hello,

I still have the same problem with pgf 2.10.

The example below gives me the same error:

! Undefined control sequence.
\pgf@sh@bg@rectangle callout ...f@sh@np@\pgf@test
\noexpand \endcsname }\ede...
l.14 the test};

What is the version of pgf where this bug is fixed?

Thanks in advance!
--
WBR & WBW, Vitaly

Vitaly Repin

unread,
Nov 3, 2013, 8:46:40 AM11/3/13
to
Hello,

Reported a bug against pgf: https://sourceforge.net/p/pgf/bugs/278/

I hope this time it will be fixed in their code.

On Friday, November 1, 2013 11:49:08 PM UTC+2, Vitaly Repin wrote:
> I still have the same problem with pgf 2.10.
> The example below gives me the same error:
> ! Undefined control sequence.
> \pgf@sh@bg@rectangle callout ...f@sh@np@\pgf@test
> \noexpand \endcsname }\ede...
> l.14 the test};

> What is the version of pgf where this bug is fixed?
0 new messages