Code node parsed but well compiled

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. Write this : 
%%%%%% cut %%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\tikzset{
  double ligne/.style args={#1 colored by #2 and #3}{
    -,line width=#1,#2, 
    postaction={draw,#3,line width=(#1)/3,
                shorten <=0*(#1)/3,shorten >=0*(#1)/3}, 
  }
}

\begin{tikzpicture}
\draw[double ligne=5pt colored by black and red](0,0)--(2,0);
\end{tikzpicture}
%%%%%% cut %%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Then in the "start" command prompt i read: 

"Couldn't parse code. MismatchedTokenException: Expected token '='. Instead 
found "args" which is of type ID in line 2 at position 22."

But all the job is perfectly done and the expected output is perfect.

Thanks for you help and thanks a lot for this great software !

Original issue reported on code.google.com by Benjamin...@gmail.com on 16 Jan 2013 at 8:23

GoogleCodeExporter commented 8 years ago

The title should be "Code not parsed but well compiled" instead of "Code node 
parsed but well compiled". Sorry for that typo.

Original comment by Benjamin...@gmail.com on 16 Jan 2013 at 3:30

GoogleCodeExporter commented 8 years ago

That syntax is currently unsupported.... (and frankly, I didn't know it 
existed).
I put it on the Todo list.
Thanks for the report!

Original comment by t.willwa...@gmail.com on 17 Jan 2013 at 8:23

GoogleCodeExporter commented 8 years ago

Thanks for our quick answer.
I have discovered this syntax very recently also.

Original comment by Benjamin...@gmail.com on 18 Jan 2013 at 3:09

rmennes / tikzedt

Code node parsed but well compiled #48