This is extremely annoying: If I have a glyph used as a component somewhere, which is not automatically aligned, and I then rename the glyph, the component is automatically aligned.
For example, I have nine.osf, which contains the component nine.tost, which has automatic alignment disabled and is spaced proportionally. I rename nine.tost to nine.tosf. Now, the component used in nine.osf becomes automatically aligned.
This is a really annoying bug. Any chance this could be fixed?
Just to be sure I understand the setup, could you send me a file?
I suspect it to be caused by the different defaults for glyphs with tabular suffixes. But I would expect it to be the other way around (when renaming from .tosf to .tost).
Sent. Sorry for the delay.
Any chance this could be fixed? It doesn’t only apply to numbers. I also tried with other glyphs. For example, I received a project with .denominator and .numerator glyphs, which I renamed to .dnom and .numr. In the fraction glyphs, where automatic alignment was deactivated, it suddenly got activated.
The renaming changes the “case” of the glyph (.tnum has no case, but .tf is upper case). That influences if a component is aligned or not. I have a fix for it, but it is probably cause more issues than it solves as it changes behavior.
How about a message then with a note what will happen and let the user decide?
I agree that auto alignment should not be forced if it wasn’t set intentionally when it might cause components to shift (likely without noticing)