marmotghost
marmotghost
I agree with all your observations, yet want to add that defining a code that inserts a path as in ``` \tikzset{my key/.code={% \path[reset cm] coordinate (a); }} ``` and...
I agree with you. It is the case that many different libraries have been written by different authors. These libraries are great and overall work fine, and have been tested...
Thanks! Interestingly, if you use the "recommended" way to do the same the problem disappears. ``` \documentclass{article} \usepackage{tikz} \begin{document} \tikzset{my key/.style={insert path={% [reset cm] coordinate (a) }}} \begin{tikzpicture} \draw (0,0)...
Yes, but you also set `a` twice. If you call the coordinates differently, you get all sorts of effects (but I agree that this should not be the case). ```...
I agree with @ilayn. However, one lesson I learnt is to **never** add transformations to the ambient `tikzpicture`. Much worse problems can arise. If you add `scale=0.6` to the options...
I might be too naive, but I think you are expecting a bit too much. (It is not my intention to downplay the capabilities of the library!) You need to...
@Mo-Gul I am really just guessing. However, you need to perform two steps. 1. Find the intersections. 2. Construct new subpaths that follow the original paths between those intersections. The...
@Mo-Gul I'd like to reiterate because the above comment may sound too negative. I am not at all negative. Rather, if you look at section 5.7.7 of the pgfplots manual...
@ilayn I would be willing to make a $100 donation to the marmot recovery foundation for the information what Don Knuth, Leslie Lamport, Heiko Oberdiek and Till Tantau *really* think...
@ilayn If true, this would be a pity. I am using what they have created on a daily basis. For work and for recreation. It is remarkable that there are...