[Netron-graphlib] Bezier connections and a little inquiry

[Francois V. <Fra...@sk...>]

(Posted in the forum as well)


While looking at intermediate connection points (it's finished by the way) I
was wondering how to implement curved connections. It's actually an idea I
had a long time ago; the GDI library allows you to draw Bezier curves but
there is no parametrization. For example, what are the coordinates of the
intermediate points if you pass a few (PointF) points to the
Graphics.DrawBezier method? Annoying thing, so I developed my own version.
You can find it here: http://netron.sf.net/downloads/BezierControl.zip
It's not integrated in the graph library, though it's now a piece of cake to
do it. If you look at the code of the Bezier control you 'll notice that it
contains the essential of the graph control: how to use the mouse events to
control GDI objects.

Concerning the difficulties with the cursors, I shifted all cursors to the
upper-left corner and I hope this helps. Actually, are the cursors OK for
you? 

I'll look at the other issue/bug you raised tomorrow (Martin). 


Now, a little story.
Had some feedback from some co-workers in the office who discovered I'm the
owner of Netron (argh, don't like to be discovered). Surprising thing is
that to many people it's not obvious what the graph library is and if they
know they find it too difficult to understand. Kinda shocking to me. I
really try to make it accessible by means of various papers and examples, a
lot of Wiki pages, forum, news list etc....seems still too abstract for
some. Well, maybe I've to conclude that it says more about those people than
about the library. Not sure though. From someone in the forum I understood
that the architecture paper is a blessing and I should finish or add
tutorials...
So, my question to you (who's leastening, I don't know): is the graph
library complicated? 

I sometimes have the impression that by releasing the source code people get
confused. If you buy a control and you get a CD with example and
documentation but no code things seem more transparent. In trying to explain
things in depth some (most) get lost, no?

Keep well, Francois.