Re: [graphviz-interest] Crossing vs. edge length

John Ellson <[email protected]>
Newsgroups gmane.comp.video.graphviz
Message-ID <[email protected]>
Anton,

It sounds like you are getting different results than for the modified
graph I attached to my previous posting?

You've made other changes ... I'm getting lost ...

John



On 08/14/2013 12:45 PM, Anton Shepelev wrote:
> John Ellson:
>
>>> Is  there  a  way  to  tell graphviz to prefer a
>>> slightly longer edge to four  additional  cross-
>>> ings?   In  the attached examle (for dot.exe), I
>>> want the edge from ep12 to INTOBJ1 to  go  round
>>> the "DB1 Tables" column from the left, so as not
>>> to cross any edges.
>>>
>>> Sorry for the messy code, I'll appreciate advice
>>> on cleaning it up.
>> One,  inelegant  trick is to add an invisible node
>> as a waypoint for the edge.
> Thank you for the reply.  After several attempts  at
> this, I have failed to produce useful results with a
> waypoint, and a question about  gv's  behaviour  has
> arisen.   In  the attached example, INTEXPOBJ is the
> last element in DB1 Tables.  I want to add  waypoint
> WP below it via:
>
>             INTEXPOBJ -> WP1 [weight=1]
>
> but  this  rearranges the column's nodes.  Why?  You
> can check it yourself by uncommenting line 42.
>
> The other edges in the column have a zero weight  so
> that  gv  can allocate them as it thinks best, but I
> don't think attachiing a dandling node  at  the  end
> should cause the re-arranging anyway...
>
>> I  also  suggest  reversing  some  edges and using
>> [dir=back] instead of forced edges to :e ports.
> Following your suggestion produces slightly  differ-
> ent  results:  the edge no longer joins the node ex-
> actly at the ceter.
>
>
>
> _______________________________________________
> [email protected]
> http://lists.research.att.com/mailman/listinfo/graphviz-interest

_______________________________________________
[email protected]
http://lists.research.att.com/mailman/listinfo/graphviz-interest
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.