Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disabled custom parameters are treated as enabled #809

Closed
justinpenner opened this issue Sep 19, 2022 · 1 comment
Closed

Disabled custom parameters are treated as enabled #809

justinpenner opened this issue Sep 19, 2022 · 1 comment

Comments

@justinpenner
Copy link

Would it be possible to add/fix support for disabled custom parameters? It's handy to disable a custom parameter in Glyphs, but instead I have to delete the custom parameter if I want glyphsLib to ignore it.

After digging around in glyphsLib I can see that there seems to be partial support for it, but it isn't working properly. For example, if my .glyphs source contains:

customParameters = (
{
disabled = 1;
name = glyphOrder;
value = (
x,
y,
z
);
}
);

…then glyphsLib outputs a lib.plist containing:

<key>public.glyphOrder</key>
<array>
  <string>x</string>
  <string>y</string>
  <string>z</string>
</array>

And if I load the same .glyphs source as an object, I can see that GSCustomParameter does seem to have a disabled property, but the value is False when it should be True.

>>> vars(font._customParameters[0])
{'name': 'glyphOrder', '_value': ['x', 'y', 'z'], 'disabled': False}
@khaledhosny
Copy link
Collaborator

khaledhosny commented Oct 3, 2024

Duplicate of #905

@khaledhosny khaledhosny marked this as a duplicate of #905 Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants