Shift-alt dragging isn't a good solution: if you shift drag towards the line, it adds a new point.
I should also add the shift dragging the origin point created a new point which is super annoying. I'm not sure why that affect would be desirable.
Start points have many special properties:
- they're more likely to produce interpolation errors on adjacent curves
they behave differently when dragging, shift dragging etc.
they don't work well with bold or outline
if a start point is a triangle BCP, if doesn't show as a triangle depending on the path direction
optimize won't optimize them*
Did I miss any?
I would like FontLab studio to treat start points like regular points. Of course some point has to be the start point, but I want the way I interact with start points to be the same as any other point.
Then there's the 90 degree "snaps" when you double click square points on cusps. They only happen once in a while (I see them only 3-4 times a week). The FontLab interface is organic and strange.
One more complaint about shift dragging: sometime shift-dragging a triangle BCP locks down the handles and sometimes it doesn't. I haven't figured out why it sometimes works and sometimes doesn't work. It's very frustrating. You go to click-drag a triangle point and hope the handles will stay locked down. When it doesn't, you undo and try again. It's part of the way I've learned to work with FontLab but it makes no sense. Why does are the handles
sometimes locked? It's not related to whether it's a start point or not. I have no idea why it does this. It's really, really annoying.
* If there are several redundant points on a straight line and one of them is a start point, optimize won't remove the start point. If a start point is along a curve, optimize won't remove it.
