You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I'm having a slight issue with your materialskin v2 nuget package in visual basic.
Overall everything works fine for for the most part, but users of my application on foreign computers have strange font issues, here's a link with how the interface is showing up for them: https://imgur.com/a/N4EuJWS
As you can see in the image it's mainly in the labels? All the other controls show up mostly fine. But its like all the labels are off by one character.
Any idea how to fix it? Or what the problem could be?
The text was updated successfully, but these errors were encountered:
Hi @tnil25 .
This project is not anymore maintained. The owner of the fork already wrote that in Readme.md file, which you'll find in the main webpage. So, even if it will be somehow repaired by someone, this will not be merged. You'll have to use something else for your GUI.
Hi @tnil25 . This project is not anymore maintained. The owner of the fork already wrote that in Readme.md file, which you'll find in the main webpage. So, even if it will be somehow repaired by someone, this will not be merged. You'll have to use something else for your GUI.
Regards, Vali
I'm experiencing the same symptoms. It's really sad that this library has been shut down. Is there at least a fixed version by someone?
Hello, I'm having a slight issue with your materialskin v2 nuget package in visual basic.
Overall everything works fine for for the most part, but users of my application on foreign computers have strange font issues, here's a link with how the interface is showing up for them: https://imgur.com/a/N4EuJWS
As you can see in the image it's mainly in the labels? All the other controls show up mostly fine. But its like all the labels are off by one character.
Any idea how to fix it? Or what the problem could be?
The text was updated successfully, but these errors were encountered: