> > Do you need this for all arrow types (some new mechanism needed) or just the
> > 'standard' -> arrow (just one new arrow type)?
> I would need it for only 2 arrowtypes, the hollow-triangle arrow ( --|>|> )
> and it's filled counterpart. The 'standard' -> arrow isn't used for my
> application.
> ...
> Why is it harder for all but the 'standard' arrow?
I think the point is: It's not any harder, but having a double-headed
version for every type of arrow adds clutter to the user interface.
If lots of double-headed versions are needed, it would be better to
rewrite the draw_<type> functions to accept an additional parameter
indicating double-headedness rather than make a whole new
draw_<type>_doubleheaded function. Of course, then you have to put
a button somewhere on the user interface to set the value of the
double-headedness parameter passed to the draw_<type> function.
David
