contextual tools for path nodes

[GoogleCodeExporter]

fields for
- x,y values of point
- x-diff, y-diff (when dragging)

- add button (when 2 adjacent nodes are selected, creates a new point
in-between with properties inherited form both)
- separate (when 2 adjacent nodes are selected, deletes the segment that
links them)
- delete button (to delete a control point)
- join with (when any 2 points are selected (even from different paths),
links the points with a line that inherits properties from both paths (if
different)) 

(for both usecases I'm not sure about the resolution of property-merging
process)

Original issue reported on code.google.com by Christia...@gmail.com on 13 Aug 2009 at 12:53

[GoogleCodeExporter]

Original comment by codedr...@gmail.com on 13 Aug 2009 at 1:58

• Changed state: Accepted
• Added labels: NeededFor-2.4, Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

In order to plot out Path Editing a little better, I've made separate issues 
for some
of this.  The Delete and Clone context tools for path nodes will be handled as 
part
of Issue 117

Original comment by codedr...@gmail.com on 24 Aug 2009 at 8:40

[GoogleCodeExporter]

I think the only things not implemented now are:

 * the "Join" function, which is not really a high priority to me since the user can
just delete a node.  Being able to join from two different paths is definitely
outside the scope of the 2.4 release anyway.
 * the "Separate" function,  which could be achieved, but again is not a high
priority to me (someone feel free to chime in).  It's possible this could be 
done by
adding a third type of segment (Line, Curve, Jump?) which translates the 
segment into
a Move.

I'm putting this bug into NeedsInfo and clearing the 2.4 flag for now.  Please 
chime
in on the bug.

Original comment by codedr...@gmail.com on 13 Oct 2009 at 3:57

• Changed state: NeedsInfo
• Removed labels: NeededFor-2.4

[GoogleCodeExporter]

Closing this issue due to lack of input.  This doesn't mean we won't one day
implement 'join' or 'separate', but that this issue is too old and contains too 
many
requests.

Please feel free to open up other issues on specific requests (issues need to 
be a
little tighter in scope).  Thanks!

Original comment by codedr...@gmail.com on 9 Jan 2010 at 11:02

• Changed state: WontFix

[GoogleCodeExporter]

i see this with a new comment in October, but i never got announced.. :( 
the problem is a little more complex than i liked to admit.. it would make more 
sense
to "separate" objects "by intersection" with other objects (with a rectangle)
also we could think about joining 2 nodes by inclusion into a rectangle.

but.. later into development 

Original comment by Christia...@gmail.com on 10 Jan 2010 at 12:21

[GoogleCodeExporter]

no worries, Christian!

Original comment by codedr...@gmail.com on 10 Jan 2010 at 3:55