Add X opaque, Parawidth and Paraweight to js.

[dberlow]

When registered axes are adjusted, these three axes are not responding and should

Let me know, thanks.

[ghost]

@asaumierdemers is there some new parametric math I need?

Also see Issue #17 which I did last night, which flips the previous behavior of the composite/parametric axes. Basically now the composite axis values are used in the actual CSS, with the parametric axes staying at their defaults (although the sliders move visually), until you actually adjust a parameter indivdually.

[dberlow]

Specifically, when using the opsz slider, starting at 72 pt, the xopq's slider does not change from "88" until 14 pt., while I can see that the xopq value in the fonts is changing throughout opsz.

Specifically, Para weight needs to be hooked up directly to wght. So if either one moves, the other goes along. Right now, if you set wght +1, and then set paraweight +1 too, you get a really heavy font, double deltas, essentially.

Specifically, Para width needs the same, being chained to wdth.

On Thu, Mar 1, 2018 at 2:01 PM, Chris Lewis notifications@github.com wrote:

@asaumierdemers https://github.com/asaumierdemers is there some new parametric math I need?

Also see Issue #17 https://github.com/TypeNetwork/variable-type-tools/issues/17 which I did last night, which flips the previous behavior of the composite/parametric axes. Basically now the composite axis values are used in the actual CSS, with the parametric axes staying at their defaults (although the sliders move visually), until you actually adjust a parameter indivdually.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/TypeNetwork/variable-type-tools/issues/22#issuecomment-369694842, or mute the thread https://github.com/notifications/unsubscribe-auth/AB3ajnReis3A3R_DDmeTcO8sUMWw9hLfks5taEVzgaJpZM4SYiPm .

[ghost]

Yeah, the current math I have for opsz only has xopq changing below 14 and not above. @asaumierdemers can let me know if I have out-of-date numbers.

I'll configure the P axes to mirror wght and wdth as you said.

[ghost]

What's the relationship between the min and max of the different scales of the registered and P axes? Straight linear?

• wght: 100–900, default 400
• PWGT: 38–250, default 88
• wdth: 35–100, default 100
• PWDT: 60–402, default 402

[dberlow]

I’m pretty sure that’s correct

Sent from my iPad

On Mar 1, 2018, at 4:59 PM, Chris Lewis notifications@github.com wrote:

What's the relationship between the min and max of the different scales of the registered and P axes? Straight linear?

wght: 100–900, default 400 PWGT: 38–250, default 88 wdth: 35–100, default 100 PWDT: 60–402, default 402 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[asaumierdemers]

@chrissam42 @dberlow The Default and opszmax have the same stem weight. That's why xopq isn't changing above the default 14pt. If you look carefully you see the contrast and width changing, but not the stem weight. See image:

[dberlow]

Thanks, I looked at it 10 times and I couldn’t tell. Will fix it in the next version.

Sent from my iPad

On Mar 2, 2018, at 9:51 AM, Alexandre Saumier Demers notifications@github.com wrote:

@chrissam42 @dberlow The Default and opszmax have the same stem weight. That's why xopq isn't changing above the default 14pt. If you look carefully you see the contrast and width changing, but not the stem weight. See image:

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[ghost]

I hooked up Para Width and Para Weight to their counterparts, but something is off. When you adjust either of the P values everything goes wonky, even though the numbers haven't changed.

It seems to have something to do with YOPQ being way too low, same thing we were seeing in Safari earlier.

[asaumierdemers]

@chrissam42 can you post a screenshot?