When class A inherits, extends or includes class B we currently draw a dependency X from A to B.
We show a dependency Y from class B to class A when class B calls some method of class A (like in the template method pattern).
So in this cases the relationship between class A and B becomes bidirectional.
The diagram would be clearer if we remove dependency Y and just leave X, given that we somehow indicate that dependency X is based on inheritance/extension/inclusion.
So this feature will be done after issue #3
Ah I see. Is there a quick fix or workaround for this? It seems to be really messing up the graphviz ranking on my graph.