Hangman

The beauty of the Affinity apps perhaps...

I think (rightly or wrongly) this is because as soon as you adjust any of the variables the font variant no longer has the same internal name. I think (again rightly or wrongly) it's the same as applying an adjustment to a variable font, exporting it to a PDF file and then opening the exported PDF file in one of the Affinity apps, the font is shown as missing because as soon as you make any edit to the font, depending on the changes made, the internal filename changes, e.g., Amstelvar_400wght_100wdth_12opsz_0GRAD_562XTRA_176XOPQ_124YOPQ_500YTLC_750YTUC_767YTAS_-240YTDE_760YTFI changes to... Amstelvar_400wght_91.25wdth_35.2opsz_60GRAD_497.8XTRA_226.25XOPQ_79.35YOPQ_495YTLC_850YTUC_862.25YTAS_-337.1YTDE_885YTFI and... RobotoFlex_103.2opsz_400wght_-130GRAD_75.4wdth_-6.5slnt_96XOPQ_79YOPQ_468XTRA_712YTUC_514YTLC_750YTAS_-203YTDE_738YTFI changes to... RobotoFlex_12opsz_400wght_0GRAD_100wdth_0slnt_96XOPQ_79YOPQ_468XTRA_712YTUC_514YTLC_750YTAS_-203YTDE_738YTFI so subsequently Font Manager sees this as a missing font in the same way it would see a static font as missing were it not installed... Just my best speculation...

Is this when opening a PDF with the embedded variable font? It will be missing if that's the case based on the unique filename allocated to the static instance of the font generated on export not matching the source filename for the font... Preflight throws up no errors and Save as Package shows the fonts with a green tick...

To be honest I think Font Variations would be more useful as a studio panel in the same vein as the Typography panel...

So it does, I was convinced when I tried that earlier it didn't work!!

Possibly because the slider starts mid-way between the two tick marks, i.e., at 400 so moving right half a tick mark gives you 420, moving left by half a tick gives you 380?

Another question... When many variables are applied the export preview and the physical export are very slow for a really simple file i.e., twenty instances of the letter A using Roboto Flex each using a different Optical Size, is this to be expected owing to the conversion to static instances of the font with fixed settings?

I made a simple PDF export test to see how the variable font information is labelled... Interestingly: Acrobat Reader fails to render or identify any embedded fonts and shows a blank page (assume this is an Adobe issue) Apple Preview shows the fonts but doesn't provide an option to see which fonts are embedded Foxit PDF Reader shows and identifies the embedded font info PackZView shows and identifies the embedded font info

Another question... Is the Font Variation panel supposed to show transparency on Mac when accessed from the Context toolbar? This feels very out of character with the rest of the UI...

Yep, completely missed it...

Hi @anto, I reported that as well here yesterday...

Feature request... A keyboard shortcut (Alt or Cmd) to disable the defined stepping when dragging the sliders, i.e., to enable the completely smooth transition of the variable between values as per Google Fonts sliders...

Hi @DarkClown, This has already been logged as a bug on Windows under AF-2789.

Of course, apologies, I had no desire to complicate things so will do, though slightly confused as this new thread was specific to a different issue, i.e., the 0% addition...

Hi @Sean P, The issue seems specific to the first three default 'Stylistic Sets' in the panel though it affects a fourth if added as well... If you click and hold the Minus button for three seconds it will happily delete the first three items correctly, though I guess that is just accounting for the natural delay seen. If you add additional 'Stylistic Sets' using the add button so you have for example twelve in the list, clicking the Minus button normally will correctly delete 'Stylistic Set 12' through to 'Stylistic Set 05' but you get the delay on 'Stylistic Set 04' to 'Stylistic Set 01'. In Light Mode, you see a dark grey horizontal line added beneath the preceding 'Stylistic Set' when the Minus button is clicked normally which I assume is just the panel background showing through... Would this still be considered a bug and logged to be fixed bearing in mind it is Monterey specific so perhaps a slight outlier? TSE Variants.mp4