I often vary the numbers in Fit curve (56%, 75% are defaults I think) depending on the typeface I am working on.
I sometimes put a note in File Info to remember for later, but it is somewhat tiring to keep track of across a number of font families and to make sure I am using the same values as before.
Any chance to have a custom parameter in Font Info that would override and remember those values for a specific font?
I don’t think there is an option in font info. You can use the Terminal to create a special Glyphs-launcher that opens Glyphs with a specific Fit-Curve configuration.
Here is a movie how you can do this (description below):
Open the Terminal app and go into your project folder (type cd ‌ ‌and drag your project folder into the Terminal window).
Type cat > Glyphs. “Glyphs” is the name of the new launcher file.
Change the min and max values in the code above to the values you want. If you are unfamiliar with editing in the Terminal, past the code to a text editor like TextEdit or Pages first, change the percentages, and copy ’n’ paste into the terminal.
Press Control-D in the Terminal to end the input and create the launcher file.
Enter chmod +x Glyphs and confirm with Return.
You can now double-click the launcher file in your project to launch Glyphs with the specific Fit-Curve configuration.
Note that this is just a workaround and has many inconveniences. But this is the best I can think of for now.
It’s a workaround. A cleaner solution would be something like TextMate’s .tm_properties system where variables are defined and inherent throughout a directory structure. But that would necessitate significant changes to Glyphs itself.
I though about adding the values to either a custom parameter (pro: no new UI needed) or userData (would need a UI or scripting solution to trigger it but would be a bit cleaner?). I though about adding an API to have a pallet configuration button (like in Adobe apps). That could be used to switch from local to global values.
Apparently I am the first one/only one to raise such request so I think it would be more than sufficient to just have a custom parameter option. I am familiar with Terminal et c., but the critical part is to have it written in the .glyphs file itself so I can track it with Git easily (and not have separate files that would create more confusion down the road).
In almost all cases, the values are stored in the user defaults. If you need specific values for a font, it needs an action to make it font specific. The easiest to do so is adding a custom parameter.