The arrow tips of TikZ path don't recalculate the bounding box set arround the picture. Therefore, Arrows at the boarder get cut in half when e.g. the standalone class is been used. An possibility is to draw within the minimal or some other class with doing a pdfcrop afterwards, but I think thats not a solution for all time.
The behavior for sure will confuse people which want to draw standalone images.
The problem is further discussed on the following links:
http://tex.stackexchange.com/questions/86521/tikz-external-figure-gets-cropped?lq=1
and (as it seems) the same problem for shadows: http://tex.stackexchange.com/questions/98525/pgf-umlsd-and-externalize?lq=1
Thank you very much for such a great project and for your efforts.
Yeah, not quite easy to achieve while keeping reasonable performance. I put this "on hold" with high priority.
This is now supported in the CVS, but not yet documented. Also, the old arrow tip code needs to be adjusted, I am working on this as time permits. But, basically, the problem is solved.
Thank you very much. I will spread the word. Great, that you handle feature requests that fast.
Hi, is this still unfixed in the current CTAN verison?
With an up to date TeX Live (TikZ version 3.0.1a) I still get the problem describet at http://tex.stackexchange.com/q/86521/4918
Regards,
Tobi
This is fixed, but you need to say \usetikzlibrary{arrows.meta}. For reasons of compatibility, old code will produce exactly the same bounding boxes as before (otherwise, all sorts of havoc would result in pictures and documents that rely on the old computations). All arrow tips defined in the new library (and, when it is used, also the normal attow tips) take the bounding box computation into account.
Great! Thanks for the respones :-)
Is there anything else I have to think about, when loading the new library in an older document (except the chnageing bounding boxes)?
Alright, I found out that I have to replace the “old” arow head names with the new ones frome
arrows.metato make it work.