User Interface/Functionality
Abort! should abort painting and Playback
Add a STUFF button to go directly from GG to Tioga.
Find problem with BiScrollers keeping top of viewer stationary when resizing viewer. PROBLEM is an interaction between BiScrollers and GGContainer. Mike Spreitzer and Eric must resolve.
Deselection of objects should terminate FollowColorTool (invoke FromColorTool automatically)
Make caret snap to nearest control point or joint during trajectory/topLevel selects. Currently only snaps to joints.
During rotate, caret should stick to selected point and track the circle of rotation.
Have a keystroke to move the caret to the midpoint of the currently selected segment
Make Cntrl/ShSpace kill gravity only for the current operation, not permanently.
Using the splines, it is essential to be able to remove the control points. Otherwise, you can't really see the shape of the curve
When selecting a control point near an endpoint, the closest endpoint is often selected, as if there were a routine checking for that case first, and using a more powerful gravity function for it. An artifact of PreferPoints?
On circles and conics, once you click Conic or Arc on the menu, select the control point, since moving that point seems to be the most common thing one wants to do next.
Replace Segment only works for lines and Bezier segments. The other curve types just move a control point to the caret.
When you turn a straight line segment into a Bezier curve, why do the control points appear at (apparently) arbitrary positions off the segment? I would expect them to lie on the segment, like the initial control point for a conic.
How come CtrlDoubleMiddle and CtrlDoubleRight don't mean CopyAndRotate and CopyAndScale respectively? -- D.
This selection business is subtle. There's some hidden state here, too: the "current granularity" and the "extendable trajectory". The current granularity seems to be set by left and middle clicks (but not by deselection?), and used by right clicks. The extendable trajectory is the one in which right clicking actually "extends" rather than "adds" (iff the initial selection was a segment and the current granularity is segments??). It seems to be the first one touched when a new selection is started; when Ken and I discussed this, we thought the most recently touched trajectory might be better.
I'd like to be able to lay down arcs, rather than lay down lines and turn them into arcs
I'd like to be able to lay down points to be used as hot spots, rather than making degenerate lines like I have to now
Since the Radius: and LineDistance: lists contain rationals like 1/2, I think I should be allowed to enter a rational like "9/7" in the LineDistanceValue: field and have it work. The same goes for Slope, Angle, and Radius, of course
Model
I am making a figure with an eliptical hole. But, the standard ellipse (a scaled circle) is a slice, not a trajectory. I'd like some easy way to make it into a hole.
It would be nice to have a way to splice control points into splines.
For a variety of reasons it would be nice to indicate that the selected shapes, trajectories or segments, were no longing editable. Once they were in that state it would be unnecessary to show the control points. Also, you could freeze the shape of a trajectory or outline to avoid accidents. A frozen trajectory would still have gravity active at its joints, but would never display them. Selection feedback would be only the line-weight change.
Conics (as defined in ImagerPath) have another degree of freedom (r) in addition to the position of the control point (p1). Is there no way to adjust r? I seem to get nothing but parabolas (r=1/2).
Regarding an entire spline as a single segment was not what I expected. I selected a cyclic spline I had made, clicked Bezier in the Curve menu, and it collapsed into a single point!
It seems I can't put a hole in, say, a circle, or a circular hole in some other trajectory. Can this be fixed? Why not regard circles and other such handy shapes as canned trajectories rather than complete slices?
Bugs/Performance Problems/Documentation Problems
It took me a little while to grok the hidden state that goes into the calculation of SlopeValue:, AngleValue:, etc. Section 9.b.2 of the tutorial didn't tell me clearly enough that it was the temporal sequence that was important. It's much clearer in GargoyleDoc.
I think you need some more vocabulary for selections. Compare the meanings of "extend the selection" in sections 5.d and 10.b of the tutorial.
Tutorial 10.c: "... joints of the box." What box?
In the pie wedge example, the rubberbanding wedge is sometimes filled incorrectly. Try dragging the arc's control point upward.
On closed, smooth curves the first/last point doesn't always show as a control point. You folks XORing somewhere?
Turning on many alignment lines and circles should not cause things to go SO slowly (I often have a dozen or so hot spots and a dozen or so alignment circles at each - things slow to an absolute crawl in that situation)