![](https://secure.gravatar.com/avatar/bb65b6b3a109d97cf9f8d6c014ede042.jpg?s=120&d=mm&r=g)
On Wed, Sep 3, 2008 at 3:54 PM, Maximilian Albert <Anhalter42@...173...> wrote:
Good point. An ad-hoc [1] correction could be to store the info in a way that more closely follows 2geom's way of storing path data. Namely, when we think of the path as parametrized by time, each node is on an integer time value. I.e., the initial node is at t=0, the next one at t=1 and so on. Thus a length-along-path value of 1.8 would represent a location on the segment between the second and third node (closer to the latter). This representation is much less susceptible to length adjustments and we can deal with node insertion/deletion more easily.
I'm not excited about this. I would like to eliminate any binding to nodes completely. Nodes are awkward legacy, they should be hidden and not affect anything. All new tools we've been adding recently go in this direction: Tweak tool does not care about nodes; Spiros use nodes but they are much less clumsy than bezier nodes and easier to move around; Alt-drag node sculpting works best when you just have as many nodes as possible, ideally eliminating any difference between node and internode segment; etc.