swiftui

I would really like to hear an official statement on backward compatibility for SwiftUI from Apple. The library annotations make me think I won't like what their position will be, but I need some closure on this issue. Personally, I am looking ahead to revamping some UI code so my app will pass the fully size adaptive requirement for App Store acceptance that will be in force in April. And I need to know, is there any hope that I can use SwiftUI for it?

You're creating your own type named “Slider”, but SwiftUI already has a type named “Slider”. Your Slider type doesn't have an init compatible with the signature init(value: Binding<Double>, from: Double, through: Double, by: Double), so the attempt to create a Slider inside the VStack fails and generates the “Unable to infer complex closure return type” error.I can make your code compile by explicitly creating the nested Slider using the SwiftUI module name:struct Slider : View { @State var celsius: Double = 0 var body: some View { VStack { SwiftUI.Slider(value: $celsius, from: -100.00, through: 100.00, by: 1.0) Text((celsius) Celsius is (celsius * 9 / 5 + 32) Fahrenheit) } } }Realistically, this is not a good solution. You should not make your own type named “Slider”. You should rename your type to something else like “TemperatureControl”.

A SwiftUI file created from the default template includes a PreviewProvider guarded by an `#if DEBUG` statement. In order to include this in the binary used by Xcode's preview cancas, open your project settings, expand Active Compilation Conditions (SWIFT_ACTIVE_COMPILATION_CONDITIONS) and add DEBUG in the debug configuration.

This isn't actually about module stability, though. In spite of its name, SwiftUI isn't part of Swift (though the syntax used to declare Views in SwiftUI is part of Swift 5.1+). The functions in the SwiftUI are just new Apple APIs.Like always, these are only going to be available on existing OS releases if Apple makes new dot (minor) versions. That can make new API available for users who update to a new dot version, without a major version upgrade. That *can* happen, but it usually doesn't.(Actually, some APIs turn out to backwards compatible because they *existed* in older versions of the OS, but weren't *public*. But this doesn't happen very often.)IDK, but it seems to me that *new* apps using SwiftUI are going to start appearing much sooner than *revisions* of existing apps with SwiftUI. That's because the cost of conversion is likely pretty high, and perhaps not worth paying for code that is already working. (And it's probably easier to generalize the layout o

The most likely recommended strategy is to create a view model for each item you want to pass to your SwiftUI view, along with a datasource class with properites for a PassthroughDataSource, NSFetchedResultsController and an array of view models.Set your datasource as the results controller delegate and configure your results contrller fetch predicate. Your view model should have an initalizer that takes an NSManagedObject and sets the properties you want to display in your UI. When the delegte method is called, enumerate over the results, create view models initalized with the resulting core data objects, append them to the array, then call send(.self) on your PassThroughSubject.I usually add a createSampleData() method that populates the same array with hard coded view models initalized with test data for use with the preview provided. class MyManagedObject: NSManagedObject { @NSManaged var name: String? @NSManaged var age: NSNumber? } struct MyViewModel { var name: String var age: String init(mana

Hi guys, I'm new to Apple development world, and I'm learning SwiftUI, looking for navigation things I found this thread.Looking further I've noticed the EditMode used with the EditButton, and it uses the Environment of EditMode to toggles it.I looked in the autocomplete of the available Environment properties and found an interesting one, isPresented.@Environment(.isPresented) var isPresentedWith this property inside my detail view, I could close programmatically a Presentation View, by just callingisPresented?.animation().value = falseNow we need some lights with the NavigationButton 😁.