Posts

Post not yet marked as solved
2 Replies
Thanks for the answer.I may have realized that my need for converters is not as high as first thought.I used them a lot in Cocoa applications, but only seldom, I used two-way bindings and two-way converters.In the concrete case, I was intending to (two-way) bind a Core Data property having a binary data type (NSAttributedString) to a SwiftUI text field. But this was not possible. Instead I will embed a UITextView into SwiftUI and add computed properties to my Core Data object that converts binary data to NSAttributed strings and vice versa.Furthermore I now think that SwiftUI, because it is so fast and easy to construct new views, will make the need for converters less than previous.
Post marked as solved
2 Replies
Thanks for informing me.I looked much forward to see the SF symbols in my macOS app. That they were not scheduled was not considered.
Post not yet marked as solved
2 Replies
It chrashes.I have tried to change the code, but without any luck. Furthermore, a couple of hours ago, I tried the same in an iOS application with no problems.
Post not yet marked as solved
5 Replies
I just bought a new iMac (model 2017) with a HDD, with the intension of being ready for SwiftUI.Today was the first day, I experimented with Catalina and the new Xcode. And it did not go well.I began this work, by following the Landmarks tutorial (...), step by step, but did not come far.When trying to do Preview, compile, or start to run the simulator, my computer just stalled and became very slow.After several attempts to fix the otherwise, I gave up, and found this blog, which I hope explains the problem.
Post marked as solved
3 Replies
No, this is new to me.Thank you very much, this really saves my week.