Error with Smart Components in LTTR/INK plugin

Glyphs
1

Hello,

I’m encountering two issues while using the LTTR/INK plugin with smart components in Glyphs. Any help would be greatly appreciated!

  1. Interpolation Error with Smart Components in Glyphs 3.3.1 (3340)
    I’m using the LTTR/INK plugin alongside smart components to create a font. For the smart components, I’ve disabled the brush function in LTTR/INK. However, when I adjust the values of the smart components, I get interpolation errors.
  2. Unable to Disable Brush Function for Individual Glyphs in Glyphs 3.4 (3414)
    In the latest version of Glyphs 3.4 (3414), I cannot disable the LTTR/INK brush function for specific glyphs individually.

Has anyone experienced similar issues or found a workaround? Thank you in advance!

GG001
GG0011430×1624 97.4 KB

GG002
GG0021282×1118 67.4 KB

leetink.glyphs (4.7 KB)

2

Re-posting the same post again is not welcome. Please be patient, whoever can help you with your issue will get back to you on your post, it might take a day or two.

1 Like
3

I’m sorry I did that, I was a little anxious, now I know the rules here.

4

Maybe @xyzajacf can help.

5

  1. Can you send me the file so I can explore the problem?
    I am using the same technique without the issue.

    CleanShot 2025-05-14 at 14.30.19@2x
    CleanShot 2025-05-14 at 14.30.19@2x346×522 25.6 KB

  2. I’ve already posted about the problem, Recent (Cutting Edge) release breaks how LTTR/INK works

6

Hi Filip,

Great to see you here! I think this issue might be a bug in Glyphs, which is why I didn’t email you directly.

  1. The test file you need is already uploaded in the thread. You can download it there.
  2. I understand the method you mentioned, but the problem is that you didn’t add adjustable layers to the smart components. When you add multiple adjustable parameters, the interpolation error occurs. Please download my test file for reference.

Thanks!

2025-05-14 21.40.59
2025-05-14 21.40.59800×520 60.9 KB

7

You know that you can do the same thing much easier without lttrink (not saying that you shouldn’t use it)? You could use the build in path offset. And have a look into corner components.

8

Thank you, Georg, for your response. Yes, there are certainly more ideal ways to handle the test file I provided. However, this file isn’t my actual project—it’s just a sample created to help illustrate the issue clearly. In reality, this problem has been troubling me for a long time, which is why I’m seeking help here. When using LTTR/INK to design Chinese fonts, some strokes cannot meet my design requirements with LTTR/INK alone, so I’ve been using smart components to work around this.

10

Bonjour à vous
Moi aussi, depuis un moment j’ai un problème avec LTTR/INK
LTTR

11

I’ve just replied to you by e-mail. Your issue appears to be different from the one reported by @7canfei.

1 Like
12

I can also reproduce the the issue with the unintentional application of LTTR/INK strokes in the cutting-edge build as reported by @7canfei and @xyzajacf, whereas it appears correctly in older builds.

@GeorgSeifert, could you please take a closer look at the issue? If it turns out to be something that needs to be addressed on our side, I would appreciate any insights you can provide, as well as access to a cutting-edge build to help with debugging. Thank you.