swiftui

I'm also looking for a way to do this. I assume that it's not possible with the currently released version of SwiftData/SwiftUI, and that you'd need to drop back to manually sharing a model container somehow, or present the content that should have been in a separate window in a sheet, meaning you can't present more than one at a time. It's quite limiting.

It looks like it does have to do with how the button's label is declared. Here's my post about another bug where a button's hit target shrinks based on its label declaration: SwiftUI Button with Image view label has smaller hit target So if I change this sample code to use a label: closure with a Label() view, the button does appear gray when disabled. Interestingly though, it still responds to taps with a bounce animation, even though the action isn’t triggered. That’s still inconsistent with how disabled buttons behave outside of a toolbar. Also, the button grows slightly wider when disabled. Code var body: some View { NavigationStack { VStack { Button{ print(Body button tapped) } label: { Label(Body Button, systemImage: checkmark) } .labelStyle(.titleOnly) .buttonStyle(.borderedProminent) .disabled(isButtonDisabled) Toggle(Disable buttons, isOn: $isButtonDisabled) Spacer() } .padding() .navigationTitle(Device: (osTitle)) .navigationBarTitleDisplayMode(.large) .toolbar { ToolbarItem { Button { prin

I’ve run into a similar issue in a macOS app and ended up rethinking how to use SwiftUI’s focus system. The app has the usual triple-panel layout: sidebar, content, inspector. The content is two tables, either of which can be focused. Each table has a TableController, exposed via .focused(). The inspector reads the focused controller to update its display, and the sidebar shows its selection—both via @FocusedValue. On paper this works, but there’s a catch: when the sidebar or inspector itself gains focus (e.g. a text field), the focused table controller becomes nil. I tried various .focus modifiers but could never get the behaviour I wanted. What I really needed was a property influenced by focus but not identical to it. For example: Use the focused table controller if one exists. Otherwise fall back to the last focused table controller. Add other rules as needed. The solution was to introduce an active table controller managed by an @Observable object in the environment. The sidebar and inspector ob

ForEach(items) uses the item identifier to identify the destination view. When you change the item name, the item identifier doesn't change, and so SwiftUI doesn't guarantee to update the destination view, which explains why the destination view doesn't show the latest change. You can fix the issue by converting the destination view to a separate custom view, and in the custom view, annotate the item with @ObservedObject which tells SwiftUI to observe the properties of the item (and update the view for any property change), as shown below: struct EditView: View { @ObservedObject var item: Item var body: some View { VStack { Text(Item (item.name ?? unnamed) at (item.timestamp!, formatter: itemFormatter)) Button(Add '?') { item.name = (item.name ?? ) + ? try? PersistenceController.shared.container.viewContext.save() } } } } struct ContentView: View { ... NavigationLink { EditView(item: item) } label: { ... } Best, —— Ziqiao Chen  Worldwide Developer Relations.

Sorry for not being clear. As an example, assuming you have some SwiftUI views that render the relationship, and the views accept only an non-optional array, it will make sense that your SwiftData model creates a computed property to wrap relationship. Here, the Swift views are the other part of your app that prefers to consume a non-optional array. I hope this makes the point clear. Best, —— Ziqiao Chen  Worldwide Developer Relations.

[quote='860800022, reglot, /thread/802423?answerId=860800022#860800022, /profile/reglot'] this fires when AVSpeechSynthesisVoice is initialized inside of an asynchronous context. [/quote] Yeah, that’s the sort of thing I saw expecting. And with that hint I was able to reproduce this trivially: Using Xcode 26.0 on macOS 26.0, create a new project from the macOS > App template, choosing SwiftUI as the UI. Add this code to the VStack in ContentView.swift: Button(Test) { Task { let voice = AVSpeechSynthesisVoice(language: nil) print(voice) } } Choose Product > Run. Click the Test button. I’m not sure whether I’d consider that a bug or not, but it definitely warrants deeper consideration from the engineering team responsible for that code. Please file a bug about this, making sure to include a reference to this forums thread and also attach a sysdiagnose log taken shortly after reproducing the issue. I’d appreciate you posting your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo

Well Apple has pretty much dropped Objective-C and moved fully to Swift and SwiftUI becuase its faster and better to use. Worth learning it though.

OK, after quite a bit more searching, I came across several links. One of the links was Gosh Darn SwiftUI - Cheat Sheet, which the link can not be displayed here Fabula For SwiftUI Human Interface Guidelines Interactful Another link, hackingwithswift quick-start/swiftui which can not be displayed. I still have not found a guide that shows controls graphics and their usage. Jim

Depending on your minimum deployment version, isn't it just the matter of a elimination game with UIDevice.current.name? import SwiftUI struct ContentView: View { var body: some View { VStack { ... } .onAppear(perform: { let device = UIDevice.current print(1 (device.name)) // iPhone 16 Pro print(2 (device.systemName)) // iOS print(3 (device.model)) // iPhone print(4 (NSUserName())) // mobile print(5 (device.description)) // //print(6 (device.model)) // iPhone }) .padding() } }