“SwiftData inheritance relationship”

If Getting into visionOS and metal for creating games - Is there any tips or optimal apis/framework/tools that you would recommend? Easiest way to start on visionOS is with RealityKit. The GameController framework supports lots of controllers for different types of games. 200GB of Background Assets available for content rich games. Are there standard methods of achieving synchronization of state between players (specifically using VisionOS here) or is it a roll-your-own situation? For synchronizing objects in a Shared spatial environment, consider using TableTopKit, which is compatible with GKMatch in the GameKit framework. If you’re using RealityKit, you can use SynchronizationService to coordinate shared physically simulated objects. We also recommend the WWDC session: Share visionOS experiences with nearby people. Which official Metal docs or sample projects best support teams moving a CPU-centric CAD kernel to GPU-accelerated workflows on Apple Silicon The Performing Calculations on a GPU sample code show

@Jerome_Donfack There are two main requirements to use transformer in SwiftData: The type returned by transformedValueClass needs to correspond to the type you declare in the model, so it needs to be changed to NSArray.self transformedValue can only be encoded as NSData, and in CoreData, we can encode into any supported type, such as NSNumber, NSString Override class func transformedValueClass() -> AnyClass { Return NSArray.self // change to NSArray } BTW: If it is not to be compatible with your other custom data, SwiftData will use the built-in transaformer to encode [String] without using transformable

I am working with an NSAccessibilityElement that corresponds to a custom UI element that doesn't inherit from NSView or one of the other accessibility-enabled AppKit classes. I would like to update its accessibility frame as the UI element moves on the screen (so, during the animation itself), while VoiceOver is focused on this element.

Thank you again for the thoughtful response. This is the high level solution I've ended up with. To recap: This is a SwiftUI document-based app: DocumentGroup backed by SwiftData. A user will typically have only a few of these files. A file will typically have only a few thousand indexed records. Search is required for in-app use only; system-wide search is not. The application maintains a single search index. When the app launches it deletes all items from the search index. This keeps the search index clean in the case of renamed, deleted or seldom used files. A document uses the domainIdentifier search attribute set to its URL to tag all of its searchable items. When a document is opened it deletes all of its searchable items using the domainIdentifier to scope the operation. It then adds all of its searchableItems to the index. The document adds, deletes & updates its searchable items while it is open. When a document's URL changes it updates the domainIdentifier of its searchable items. In-ap

Another few small refinements - school delete rules set up I think import Foundation import SwiftData // Define School // Each School will offer a list of [Schoolclass] // Each Schoolclass will have one Teacher and a list of [Student] // Each Teacher may teach multiple classes, but only at one unique school // Each Student will attend multiple classes but only at one unique school // Bonus!! Start with the assumption that each SchoolClass instance is unique and only offered in one school, but want to expand so that a particular SchoolClass may be offered at more than one school, but have unique Teacher and [Student] for that class at each school @Model class School: Identifiable { var id: UUID = UUID() var name: String var mascot: String @Relationship(deleteRule: .cascade) var schoolClasses: [SchoolClass] // If a school is deleted, delete the classes associated with it, but leave the students and teachers all with an empty class list. // Every school that is created will have a class list, b

Another day of refining this model gets me to the following code... Please see if my comments are correct, and if I am missing something... import Foundation import SwiftData // Define School // Each School will offer a list of [Schoolclass] // Each Schoolclass will have one Teacher and a list of [Student] // Each Teacher may teach multiple classes, but only at one unique school // Each Student will attend multiple classes but only at one unique school // Bonus!! Start with the assumption that each SchoolClass instance is unique and only offered in one school, but want to expand so that a particular SchoolClass may be offered at more than one school, but have unique Teacher and [Student] for that class at each school @Model class School: Identifiable { var id: UUID = UUID() var name: String var mascot: String var schoolClasses: [SchoolClass] // Every school that is created will have a class list, but it may be an empty list init (name: String, mascot: String = , schoolClasses: [SchoolClass] = []) { s

Some will be easy to get like all teachers for a school but others will require a little more work. One important thing to remember is that you add relationships to define your models and how they relate and not for helping with some queries you might want to implement. That said, one further relationship to consider is between School and Student so that a student can only take classes that belongs to the school they are assigned to.

filterQueries is actually being passed over and processed on the daemon side Excellent. The correct answer is to create a CSImportExtension. That extension point hands you the file you're indexing, side stepping the entire issue. Looking at the documentation for CSImportExtension it appears that this is for gathering & updating information about a file, not the items in the file. The extension only gets one CSSearchableItemAttributeSet that is for metadata about the file. An object that provides searchable attributes for file types that the app supports. Even if I wanted to misuse the API just to trigger a full reindex of the file contents, due to sandbox restrictions I don't think it would be possible to open an arbitrary file. The user would have to select the file in an Open dialog. My current solution is: When a document is opened start a Task that gathers all of the uniqueIdentifiers of the searchableItems for this file from the search index (using the contentURL to filter the results). Gather the mo

You haven't told us exactly what your issue is but something I spotted with your design that I don't think is correct is the relationship between Teacher and Student. As I see it your design will be simpler and more correct if you complete remove that relationship. A teacher holds (has) one or more classes A student attends (has) one or more classes So indirectly you have the relationship between Teacher and Student via the SchoolClass model. A bit unrelated but I prefer to use the @Relationship macro with the inverted argument for one of the relationship properties since it makes the code clearer for me (and it is also helpful for SwiftData)

I ran into the same error message when using #Predicate in SwiftData @Query with Xcode 26.0 beta 2, Swift Language Version Swift 6, and Setting Default Actor Isolation on MainActore (section Swift Compiler - Concurrency). Setting the Default Actor Isolation to nonisolated and inserting @MainActor above @Observable inside the code resolved the problem.