Bad line junctions sometimes #417
Comments
|
So the original problem can be reduced to this thing: which produces: Now, the code is slightly incorrect --- The patch fixes it but it disrupts the path, unfortunately. Not sure why because I do not understand the code ;-) |
|
Now, this is a different patch (applied over the revert): diff --git a/tex/pgfcircpath.tex b/tex/pgfcircpath.tex
index a20f8b7..c6a855a 100644
--- a/tex/pgfcircpath.tex
+++ b/tex/pgfcircpath.tex
@@ -107,6 +107,7 @@
(\tikztostart) coordinate (\ctikzvalof{bipole/name}start)%necessary to get correct coordinates in the case of relative start/end or constructions like ((node1)-|(node2))
(\tikztotarget) coordinate (\ctikzvalof{bipole/name}end)
+ (\tikztostart) % go back to start
\pgfextra{
\pgfmathanglebetweenpoints{\pgfpointanchor{\ctikzvalof{bipole/name}start}{center}}
{\pgfpointanchor{\ctikzvalof{bipole/name}end}{center}}Seems to fix both things: and So... any comment? @sistlind @mredaelli @der-stefan |
|
Notice that now the original example in issue #76 compiles like this: Which is correct --- The behavior of forcing the start point at the center of the node is not standard and creates a lot of problems. |





Consider the following snippet:
If you look at the result, you have:
Now, reverting this patch: 6efc2ee
seems to fix it. My problem is that I do not understand what the patch is doing... I will try to dig into it. Meanwhile, if @sistlind is here, could you shed some light? I have seen the bug report but I can't really understand it. Doing
is expected to fail if the (node) has no border anchor anyway... or I am wrong?
I am trying to compile the manual with it reverted... let's see.
The text was updated successfully, but these errors were encountered: