Don't have the time to try "statics". I'm suspecting that it could be that VS chokes on variable fonts - period but it would take a lot of time to check it (at least 2 fonts, say Cascadia and JetBrains Mono). If this is indeed the case then it would be good to document it and place a clear warning and not go "convincing" people to install variable fonts "just because". It's colossal waste of time, not to mention frustration.
The Win itself takes the font just fine, VS shows all variations in the list bt the very sec I pick it the code display goes to Courier or whatever is VS default to make sure it doesn't go blank. VS does have a long history of not being able to handle anything beyond 4 basic variations and I'm not saying that you can fix VS - but you can check and post clear warnings instead of creating an impression that everything is in perfect order.
Cascadia family version
2111.01
Cascadia family variant(s)
Cascadia Code (the version with ligatures)
Font file format(s)
.ttf (variable)
Platform
Windows
Other Software
Visual Studio 2019 16.11.16
What happened?
Don't have the time to try "statics". I'm suspecting that it could be that VS chokes on variable fonts - period but it would take a lot of time to check it (at least 2 fonts, say Cascadia and JetBrains Mono). If this is indeed the case then it would be good to document it and place a clear warning and not go "convincing" people to install variable fonts "just because". It's colossal waste of time, not to mention frustration.
The Win itself takes the font just fine, VS shows all variations in the list bt the very sec I pick it the code display goes to Courier or whatever is VS default to make sure it doesn't go blank. VS does have a long history of not being able to handle anything beyond 4 basic variations and I'm not saying that you can fix VS - but you can check and post clear warnings instead of creating an impression that everything is in perfect order.