#13819: arrow2d path keyword is confusing
-------------------------------+--------------------------------------------
Reporter: kcrisman | Owner: jason, was
Type: enhancement | Status: new
Priority: minor | Milestone: sage-5.6
Component: graphics | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
-------------------------------+--------------------------------------------
Changes (by mjo):
* cc: mjo (added)
Comment:
For one segment, the notation,
{{{
sage: arrow2d((1,1),(3,3), control_points=[(2,3)])
}}}
makes more intuitive sense, but may not be as convenient as throwing all
of the points in the same list. When you consider multiple segments with
an arrowhead at the end, though,
{{{
sage: arrow2d(path=[[(1,1),(2,3),(3,3)], [(4,4),(5,5)]])
}}}
is probably as simple as it's going to get. In any case, we should
document how/why it works.
I was going to argue that the current syntax makes it easy to reuse an
existing bezier path, but here be dragons:
{{{
sage: bp = [[(1,1),(2,3),(3,3)], [(4,4),(5,5)]]
sage: bezier_path(bp)
sage: bp
[[(1, 1), (2, 3), (3, 3), (4, 4), (5, 5)], [(4, 4), (5, 5)]]
}}}
That probably deserves its own ticket; the `bezier_path` function should
copy its argument rather than modify the user's list.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13819#comment:2>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
