I’ve noticed on multiple occasions that the vertical position is constrained, when the desired y position is within a certain range. This can lead to errors:
This is very annoying. Is there some way to fix this? Thanks.
I read the sentence multiple times and still do not understand. What do you mean by ‘constrained’? Which position, within which range of what?
When moving the component vertically, it snaps to a specific y position, when I move it within a certain range. For instance, the component in the screenshot above snaps to y=710, when I try to move it within the y range 705–715.
This is a sensible mechanism in most cases, where components snap to a metric (exclamdown.case snaps to the cap height metric, etc., this minimises user errors). In some cases, however, the calculation is wrong and it snaps to a wrong location.
How do you move the component?
I can trigger snapping only when I move it by mouse. It works as expected with arrow keys.
Both mouse and arrow key movement lead to the same behaviour.
Moving it with arrow keys triggers an “Edited” indication in the Glyphs document, but printing component.position shows that the position doesn’t change. It sticks at 710.
When it is “wrong” where does it snap too?
I don’t know how the snapping is calculated. See for yourself:
WrongSnapping.glyphs (1.3 KB)
In the background, you can see the position of the bracketleft.case.
710 is the cap height. Why shouldn’t it not snap to it?
Because it should be a perfect 180° rotation of braceleft.case. A rotated component needs to be shifted by an amount completely independent of the metrics. See the example file.
For non-rotated components snapping is sensible. Not for rotated components.
Any chance this could be fixed? Disabling automatic alignment altogether would be a shame. Thanks!