GoogleCodeExporter
commented
9 years ago Here's some thoughts I had on the UI for this feature:
We currently show the points of the path, letting a user hover and then drag
them.
This works ok for straight line segments.
But actually the point is only _part_ of the path segment. For example, if
there are
three line segments: A,B,C then the path actually has 3 path segments: AB, BC,
CA.
For more complicated path types, the segment consists of more than just a
point. If
AB is not a line but a bezier curve, it actually has control points at BOTH
ends of
the segment.
So how to show this relationship? My current ideas are as follows:
1) we keep the points shown for ease of dragging them around. With Issue 117,
when a
point is clicked on the contextual panel updates for that point (user has
buttons to
delete or clone that segment)
2) when the user hovers over a segment (i.e. the line AB) then that line gets
highlighted. If clicked on, the contextual panel shows a control which allows
the
user to change the type of segment: line, bezier curve (maybe in a pulldown).
3) when the highlighted segment is a curve, we show the control points (at both
ends
of the segment) and give the ability for the user to drag and manipulate the
curve
4) need a keyboard way of navigating to previous or next segment when the
segment is
highlighted (maybe re-use Shift-O,P or the arrow keys?) for complicated paths
that
are hard to click
Zoom (Issue 38) will also help with the ability to fine-grain select a segment
in
complex/tight paths.
The above makes an artificial distinction between the end points of a segment
and the
segments themselves. If you want to change the position of a segment, you would
click on an endpoint and drag the point. If you want to change the curvature
of a
segment, you would click on the curve between the two points.
What do others think of this idea?Original comment by codedr...@gmail.com on 7 Sep 2009 at 4:04
Original issue reported on code.google.com by
codedr...@gmail.comon 24 Aug 2009 at 8:38