CP proposal : Keep Instances Active

[HugoJ (Hugo Jourdan)]

Hey,

This isn’t a conventional setup, but I think it might be more common than we expect.

In a project where there are two sets of instances with identical coordinates (let’s say Set 1 is the standard version, and Set 2 has ss01 activated by default), if you try to export a variable font, all instances will end up in the fvar table.

Would it make sense to have a “Keep Instances Active” custom parameter, to manually define which instances should be included in the fvar?

I noticed you recently added the “Include in fvar/STAT/static/variable” CP — is that meant to cover this situation?

[GeorgSeifert]

I just add “include in fvar/STAT…” custom parameters. That allows at least to disable one of the two sets.

[alexs (Alex)]

@HugoJ

In a project where there are two sets of instances with identical coordinates (let’s say Set 1 is the standard version, and Set 2 has ss01 activated by default)

Looks like another use case for “static setting” (as in “variable setting”) instance to be built-in…

Enhancements to the .glyphsproject format

Totally with you on that, I meanwhile added a similar functionality into Export to All Formats script and happy with it so far. It works similarly to variable instances, without the .glyphsproject because I don’t understand the concept of having instances in a separate file. In case you find it useful: How to for the script (beta): “Static Settings” allow exporting different versions of the same instances, bulk-applying different custom parameters/names/properties: Add an instance(s) with …