Search Results

I have trided multiple things but I cannot find the solutions. De left side works fine like this: struct LeftSidebar: View { @EnvironmentObject var appState: AppState var body: some View { VStack { List { NavigationLink(destination: HomeMac()) { Label(Home, systemImage: house.fill) } Section(header: Text(SF-symbolen)) { NavigationLink(destination: HomeMac()) { Label(Alle, systemImage: square.grid.2x2) } // NavigationLink(destination: NieuwView()) { // Label(Nieuw, systemImage: star) // } } Spacer() Button(action: { appState.logOut() }) { HStack { Image(systemName: arrow.backward.circle) Text(Loguit) } } } .listStyle(SidebarListStyle()) .frame(minWidth: 50) } .padding() } } var body: some View { ZStack { NavigationView { LeftSidebar() .environmentObject(appState) HomeMac() RightSidebar() } .frame(minWidth: 800, minHeight: 600) } } } But when I want to try this its not working the same.

I have tried every single thing listed above and nothing works. Deleted app and restarted my phone after every attempt Tried on wifi and then on cellular tried do not disturb/on off deleted my profiles on xcode and then re-added them None of these work. This is wild that this a real issue. Straight up cannot develop. Xcode: 15.4 osx: 14.5

Not an explanation (I am interested to read an authorised analysis, but my understanding is that calling onChange on the State var, leads TabView to reevaluate its content. Why ? That is the question ! A possible reason: as oldValue, newValue change, that forces the TabView to redraw (and reevaluate). Generally, I have noticed it is very hard (and hazardous) to try to guess how SwiftUI works to reevaluate views…

The declarations-items endpoint in the DeclarativeManagement CheckIn request returns the set of declarations assigned to the device making the request. The device will use that list to synchronize the set of declarations from the server. It is up to you to decide what to send to the device. One option is to filter the set of declarations to only those that are expected to be active on the device. The other option is to send declarations that use activations to ensure only those relevant to the device are active. For example, say you have one set of declarations for iPads, and one set for iPhones. You could create separate activations for each set with predicates that only evaluate to true for the corresponding hardware. You could then choose to send both sets of declarations to the device and let it decide what gets applied. Or, since the server does know the type of device hardware, it can choose to only send the set of declarations relevant to that hardware. Things get trickier when the factor that

That used to be true until recently. With the Observable() it is no more true. From StateObject doc: If you need to store a value type, like a structure, string, or integer, use the State property wrapper instead. Also use State if you need to store a reference type that conforms to the Observable() protocol. To learn more about Observation in SwiftUI, see Managing model data in your app.

I was puzzled by the crash when removing an added item. That had to do with the focus on the TextField… This works more properly: struct FileItem: Identifiable { var name: String var children: [FileItem]? // 👈🏻 Will be nil if child at lowest level of hierarchy ; otherwise for parent, should be [] when no child var id: String { name } } struct ContentView: View { @State var data: [FileItem] = [ FileItem(name: First, children: [FileItem(name: childF1), FileItem(name: childF2)]), FileItem(name: Second, children: [FileItem(name: childS1), FileItem(name: childS2), FileItem(name: childS3)]), FileItem(name: Third, children: [FileItem(name: childT1), FileItem(name: childT2)]) ] @FocusState private var focusedField: String? var body: some View { List($data, children: .children) { $item in HStack { TextField(, text: $item.name) // probleme : le clavier disparait à chaque caractère // Avec focused, on passe au dernier TextField .focused($focusedField, equals: item.name) .task { self.focusedField = item.name }

When you add on child line, what do you add ? A child of the parent ? A child of the child ? I need to have both for each line item. So simple! Remove some tests. Here is an updated code… struct ContentView: View { @State var data: [FileItem] = [ FileItem(name: First, children: [FileItem(name: childF1), FileItem(name: childF2)]), FileItem(name: Second, children: [FileItem(name: childS1), FileItem(name: childS2), FileItem(name: childS3)]), FileItem(name: Third, children: [FileItem(name: childT1), FileItem(name: childT2)]), ] @FocusState private var focusedField: String? var body: some View { List($data, children: .children) { $item in HStack { TextField(, text: $item.name) .focused($focusedField, equals: item.name) // avoid keyboard to disappear at each character .task { self.focusedField = item.name } // Text(item.name) // If there are no children, we cannot remove it if item.children != nil { // So it is parent, maybe with no child [] Spacer() Button(Add child) { // let's search its position in data

So, that last one FB9997771 was reported as fixed in the 2022 OS rereleases (so, macOS 13 and friends). Thank you for that detail, Quinn. I am very happy to hear that that one is officially fixed. That had caused really odd intermittent failures in unexpected areas within the JDK and had taken us a long time to narrow it down. I will run our tests against macosx 13 and higher to verify the fix. That should’ve been communicated to you but wasn’t. I’m not sure why. I’ll follow-up on that internally, just for my own understanding, but this is all about Apple internal processes so I probably won’t post any more details here. I understand. The other two are still under investigation; I don’t have any further info to share. Thank you for that update. Bug Reporting: How and Why? has a bunch of hints and tips on this front, but probably the best important is this one: If you’re filing a bug against an API, choose Developer Technologies & SDKs at the top level. This is useful. So far I've been filing it under Some