Skip to content
Permalink
Branch: master
Commits on Mar 13, 2019
  1. Renaming perspective library macros

    MaxSnippe committed Mar 13, 2019
Commits on Mar 10, 2019
  1. Correct copyright statement

    hmenke committed Mar 10, 2019
Commits on Mar 8, 2019
  1. Added perspective library

    MaxSnippe committed Mar 8, 2019
Commits on Mar 6, 2019
  1. Fix TeX conditionals on \pgfmathdeclarefunction (Eric Domenjoud) Feat…

    hmenke committed Mar 6, 2019
    …ure Request #121
Commits on Feb 28, 2019
  1. More accurate \pgfpointnormalised #518 #519 Feature #96

    hmenke committed Feb 28, 2019
    This has been a long-standing problem, that \pgfpointnormalised was too
    inaccurate.  This resulted in wrong intersection points when using the
    projection syntax.  One proposal was to replace the definition of
    \pgfpointnormalised by atan2 and cos and sin.  The prime argument against this
    was the possible performance impact.  This is a reasonable assumption
    considering the large definitions of atan2, cos, and sin.  However, in
    typesetting the manual with the new and the old definition I could only observe
    a 1% performance loss, which corresponds to 4s wallclock time on my machine.
    Since the manual has an enormous amount of TikZ figures on over 1000 pages, I
    think this performance loss can be considered negligible.
Commits on Feb 21, 2019
  1. tikzmath needs to know about fpu

    hmenke committed Feb 21, 2019
Commits on Feb 20, 2019
  1. Fix shading angle #516 (Eric Domenjoud)

    hmenke committed Feb 20, 2019
Commits on Feb 13, 2019
  1. Fix trivial typo #514

    hmenke committed Feb 13, 2019
Commits on Feb 7, 2019
  1. Missed ligature suppression for dvisvgm #473

    hmenke committed Feb 7, 2019
  2. Now I hopefully got all of the ligatures #473

    hmenke committed Feb 7, 2019
Commits on Feb 4, 2019
  1. Some fixes for the shading patch #511 (Eric Domenjoud)

    hmenke committed Feb 4, 2019
  2. \long\def

    hmenke committed Feb 4, 2019
  3. Revert "Revert "Patch for shadings #511 (Eric Domenjoud)""

    hmenke committed Feb 4, 2019
    This reverts commit cd613dd.
  4. Revert "Patch for shadings #511 (Eric Domenjoud)"

    hmenke committed Feb 4, 2019
    This reverts commit 3509712.
  5. Making the declared coordinate accessible

    hmenke committed Feb 4, 2019
    Often it is desirable to know what was the coordinate that a node (or other
    named thing) was declared with.  This is now made globally available and
    integrated into the let operation under the name \coord.  Keep in mind that
    when calling \coord on something that was not a named thing, you'll just get
    the declared coordinate of the last named thing or \relax if there was nothing
    named before.  [[ Example:
    
        \path (0,0,{cos(45)}) coordinate (A);
        \path let \p1=(A), \p2=(2,2,2) in \pgfextra{\typeout{A=\coord1,B=\coord2}};
    
    will print in the log
    
        A=(0,0,{cos(45)}),B=(0,0,{cos(45)})
    
    because \p2 is not a named coordinate. ]]
    
    Another issue might arise if the shape was not declare with a coordinate at
    all, in which case the result is undefined.  You might end up with the name of
    the thing itself or \relax. [[ Example:
    
        \coordinate (A);
        \path let \p1=(A) in \pgfextra{\typeout{A=\coord1}};
    
    will print in the log
    
        A=(A)
    
    because \p1 was not declare with a coordinate. ]]
  6. Check for \pgfpointxyz before \rawx, \rawy, \rawz

    hmenke committed Feb 4, 2019
  7. Add \rawx, \rawy, \rawz to let operation

    hmenke committed Feb 4, 2019
    There is an issue with 3D coordinates being projected onto the 2D canvas.
    There is not way to reverse the projection because a system of two equations
    (the project 2D coordinates) with three unknowns (the original 3D coordiantes)
    is underdetermined and unsolvable.  Hence I introduce these new little helpers
    which can be used to access the parsed original coordinates.  This works only
    if you use literal coordinates in the let operation, i.e.
    
        \path let \p1=(1,2,3) in ...
    
    will work as expected, but
    
        \coordinate (A) at (1,2,3);
        \path let \p1=(A) in ...
    
    will not work, because the projection has already been performed when defining
    the \coordinate.
Commits on Feb 3, 2019
  1. Disable strict nesting for now

    hmenke committed Feb 3, 2019
  2. - minor stuff

    Mo-Gul committed Feb 3, 2019
Commits on Feb 2, 2019
  1. Merge branch 'master' of ssh://git.code.sf.net/p/pgf/git

    Christian Feuersaenger
    Christian Feuersaenger committed Feb 2, 2019
  2. Merge branch 'branch_3.1_hotfix'

    Christian Feuersaenger
    Christian Feuersaenger committed Feb 2, 2019
  3. updated release file

    Christian Feuersaenger
    Christian Feuersaenger committed Feb 2, 2019
  4. enabled Mandelbrot Set for lua

    Christian Feuersaenger
    Christian Feuersaenger committed Feb 2, 2019
  5. Reenable dvips job on Travis CI

    hmenke committed Feb 2, 2019
  6. Prepared changelog for 3.1.1

    Christian Feuersaenger
    Christian Feuersaenger committed Feb 2, 2019
Commits on Feb 1, 2019
  1. Revert "Color fix for dvips (Herbert Voss) #503"

    Christian Feuersaenger
    Christian Feuersaenger committed Feb 1, 2019
    This reverts commit 4b87b9b.
  2. Merge branch 'master' of ssh://git.code.sf.net/p/pgf/git

    Christian Feuersaenger
    Christian Feuersaenger committed Feb 1, 2019
  3. Fixed regression: dvips could no longer be used (reverted 362)

    Christian Feuersaenger
    Christian Feuersaenger committed Feb 1, 2019
Commits on Jan 28, 2019
  1. Fix typo in documentation #510

    hmenke committed Jan 28, 2019
  2. Tail call

    hmenke committed Jan 28, 2019
Older
You can’t perform that action at this time.