Menu ▾ ▴

#417 Syntax error in section 100.4 of 3.0.1a manual

v1.0 (example)
closed-fixed
nobody
documentation (7)
5
2018-05-22
2017-02-05
Carl Sorensen
No

The example of defining a new arrow type foo in section 100.4 has a syntax error.

The draw section leaves out the \pgfqpoint commands, and hence the \pgflineto commands don't work properly.

That is, it should say

  drawing code = {%
    \pgfpathmoveto{\pgfqpoint{.25\pgfarrowlength}{0pt}}
    \pgfpathlineto{\pgfqpoint{-.75\pgfarrowlength}{.5\pgfarrowlength}}
    \pgfpathlineto{\pgfqpoint{-.5\pgfarrowlength}{0pt}}
    \pgfpathlineto{\pgfqpoint{-.75\pgfarrowlength}{-.5\pgfarrowlength}}
    \pgfpathclose
    \pgfusepathqfill
  },

but it currently says

  drawing code = {
    \pgfpathmoveto{.25\pgfarrowlength}{0pt}
    \pgfpathlineto{-.75\pgfarrowlength}{.5\pgfarrowlength}
    \pgfpathlineto{-.5\pgfarrowlength}{0pt}
    \pgfpathlineto{-.75\pgfarrowlength}{-.5\pgfarrowlength}
    \pgfpathclose
    \pgfusepathqfill
},

This keeps the code from compiling.

Discussion

  • Stefan Pinnow

    Stefan Pinnow - 2018-05-22

    Good catch. Thank you very much. This is fixed now.

     

  • Stefan Pinnow

    Stefan Pinnow - 2018-05-22
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,6 +1,6 @@
 The example of defining a new arrow type foo in section 100.4 has a syntax error.

-The draw section leaves out the \pgfqpoint commands, and hence the \pgflineto commands don't work properly.
+The draw section leaves out the `\pgfqpoint` commands, and hence the `\pgflineto` commands don't work properly.

 That is, it should say
 ~~~
@@ -12,7 +12,6 @@
     \pgfpathclose
     \pgfusepathqfill
   },
-
 ~~~
 but it currently says
 ~~~
    • status: open --> closed-fixed