typemytype
Variation axis warning appears to be incorrect
Version 3.115 (3.115)
I'm testing fontVariations in Drawbot, and I have come across a bit of an unexpected warning. This is drawing the result I want, but giving me a warning for my incorrect syntax:
The xprn string (in lowercase) works for what is technically supposed to be labeled as XPRN (in uppercase). However, when I do use the proper XPRN string, it no longer controls the axis:
I've figured out how to get it to work how I need for now, but this may be confusing to new users. Just thought I'd log the unexpected result here.
I'm realizing that it's slightly more complicated than I expected. Once I tried to put the variations into a loop, the xprn stopped working, and XPRN would work, so long as I made it decimals, and not quite the min or max. So, XPRN=0.01 does work, but xprn=0.01 does not.
Did you restart DrawBot after activating a new version of your font? DB looks into the actual font, but some properties may be cached by the OS from the previous session, so confusion may occur...
Sorry, I should have included that I'm on macOS 10.13.3. I have since restarted Drawbot, and I see some unexpected behavior. Granted, this may be an issue in the font, rather than in Drawbot.
As an update on this, the max does work (1.0) but the min still does not. So, in the screenshots below, you can see that the leftmost column has the "expression" axis turned all the way up when I tell it to be 0 (the minimum), but it is displayed as-expected when I tell it to be 0.01 (close-to-but-not-quite the minimum).
The 0 value is showing up as 1 in the leftmost column, even though all other values are working as expected
The leftmost column looks like I want it to, if I tell it to have a value of 0.01
This feels like a bit of an amorphous issue; sorry for that. :| I just wanted to bring this up in case others are having the same experience. I can email the font and Drawbot Files, if that would be more helpful for testing.
I can reproduce this on 10.10, the default or misvalue seems not accessible.
I've heard that it is fixed (or at least, a seemingly similar bug shown in Sketch Beta is fixed) in macOS Catalina (according to this tweet). However, I haven't yet updated my OS, so I can't personally confirm this.
