Open Sethmr opened 5 years ago
You can use ASTextNode2 instead of ASTextNode. But in my case it didn’t help me completely. The second version of ASTextNode sometimes behave itself completely different compared to the first version.
Is this #1579 ?
@atkalikov I would be willing to try this, but I literally have hundreds of cases I am working with here. Is there any documentation on the differences between ASTextNode2
and ASTextNode
?
Also, I don't know if this is any help, but .SF UI Text
and .SF UI Display
are no longer found in UIFont.familyNames
or UIFont.fontNames(forFamilyName: anyFamily)
. I think this has something to do with the SF Symbols in iOS 13.
I had test in #1579 , it fixes this issue. @bolsinga @Sethmr
@dirtmelon Would you be able to create a PR that has a test for this? It would be terrific to back fill these tests. Thanks. @Sethmr Please try with master.
@bolsinga I will attempt tomorrow.
Ran into this myself yesterday. Couldn't get it working with latest from master either. Font displayed fine without paragraph style.
Wonder if you found the same @Sethmr?
@ay8s If you look at my post, that is directly what it is saying ;)
@bolsinga It is working great in master. I'll be looking forward to the next release. I came up with a patch job that mostly is working in the mean time.
Sorry, I meant in your attempt today. Will have to dig into why it wasn't working for me with master.
I am facing the same issue. When will you guys release the new version with the fix of this issue?
Hello. Today is December 4th. Can you release at least a little hotfix for this problem?
Would love a fix. Nevertheless, great project guys! Texture makes creating iOS projects a lot of fun.
After using the XCode 11 compiler, the
.systemFont
started having incorrect cases of font app wide for us. After looking deeper into the problem, I found that every time you use the.paragraphStyle
in any way shape or form (even with an empty initializer) on yourNSAttributedString
it will cause Times New Roman to be displayed instead of SF Fonts.My team uses this extensively in our app and would highly appreciate a fix. I will attempt to find a work around in the mean time that is acceptable. Thanks for a great framework to build upon :).
Example below: