Post not yet marked as solved
Yes I am not seeing any incremental builds with 13.2, always seems to do full recompiles now. I don't think 13.1 was this bad! What a nuisance.
Post not yet marked as solved
Here is a tip - and I struggled forever.
create app iCloud containers something like this
com.company.app.dev01
com.company.app.dev02
com.company.app.devxx
com.company.app.prod
If you create the container with the wrong settings than it seems that is it ! You can't get it to show up no matter what you do except create a new one, hence the naming conventions above.
Be sure to set the access as Public in info.plist BEFORE you run the app the first time !!
Also make sure all the identifiers match up in the app entitlements and on the target Signing & Capabilities page and in the apps info.plist.
Post not yet marked as solved
You want a File Wrapper - see article linked
https://www.swiftdevjournal.com/using-file-wrappers-in-a-swiftui-app/
I see, yes I am familiar with the Core Data API to set the filename and path but I can't see any way to use that in conjunction with DocumentGroup and/or FileDocument/ReferenceFileDocument such that you can create/open the sqlite files in iCloud Drive or in the local app sandbox.
Not sure I understand how this works.
DocumentGroup provides the ability to browse/create/select a file but how do you create a new core data file or save one where there have been edits made. I don't see how you set the path to the actual file that is created/selected in DocumentGroup.
Perhaps I am misunderstanding something but don't you need to create the sqlite or binary core data file at the URL obtained/created by DocumentGroup ? Otherwise doesn't NSPersistentContainer just store the core data files in the apps default location.
I am assuming use of DocumentGroup means you can create the core data file on anywhere on iCloud Drive.
var body: some Scene {
DocumentGroup(newDocument: { Document() }) { config in
ContentView()
// injecting persistent controller into the document view
.environment(\.managedObjectContext, config.document.persistenceController.container
.viewContext)
}
}
Hi, did you ever manage to get this to work ? If so could you provide more details on how you link the core data file to the ReferenceFileDocument.
What do you do about the following ReferenceFileDocument protocol functions:
typealias SnapShot
func snapshot(...)
func fileWrapper(snapshot:...)
Post not yet marked as solved
Here is a sample app that illustrates the problem. For some reason the editor complains about the URL below so please remove the space after the https to download the test app
https ://duncangroenewald.com/files/SampleApps/CALAyerRendering.zip
Post not yet marked as solved
This is what I ended up doing - should this really be necessary ?
class ZOrderDrawingLayer: CALayer {
override func render(in ctx: CGContext) {
if let layers:[CALayer] = self.sublayers {
let orderedLayers = layers.sorted(by: {
$0.zPosition $1.zPosition
})
for v in orderedLayers {
ctx.saveGState()
let w = v.bounds.width/2
let ww = w*w
let h = v.bounds.height/2
let hh = h*h
let c = sqrt(ww + hh)
let theta = asin(h/c)
let angle = atan2(v.transform.m12, v.transform.m11)
let x = c * cos(theta+angle)
let y = c * sin(theta+angle)
ctx.translateBy(x: v.position.x-x, y: v.position.y-y)
ctx.rotate(by: angle)
v.render(in: ctx)
ctx.restoreGState()
}
}
}
}
Post not yet marked as solved
Thanks @FrankSchlegel - I will try it out.
Post not yet marked as solved
With a bit more fiddling around I get this
[error] precondition failure: invalid attribute id: 2189977
AttributeGraph precondition failure: invalid attribute id: 2189977.
And finding similar errors elsewhere I remembered that I changed a NavigationView to a HSplitView (?) which seems to behave the same . After reverting to NavigationView this crash goes away !
Is this a bug? and should I raise a bug with Apple for this ?
Post not yet marked as solved
It seems that the RAW file contains the native camera image size (sensor size) and the thumbnail contains and image that is set to the aspect ration setting that was used on the camera. So when querying the RAW files thumbnail you get the thumbnail stored by the camera but when getting the CIImage using CIFilter you get the full image i.e. native camera sensor image size.
There seems to be no RAW API to get the camera set aspect ratio but this data does seem to exist in the EXIF data XDimension and YDimension.
Hi Eskimo can you indicate whether it is possible for a Sandboxed macOS app to retain permission to files for future access. For example the user selects a folder initially and the app reads metadata from the files in the folder and keeps a database of the files. At some future point the user launches the app again and selects a database record and the app then loads that file. Currently in in subsequent file access for generating thumbnails we get the following error.
error: Error Domain=NSPOSIXErrorDomain Code=1 "couldn't issue sandbox extension com.apple.app-sandbox.read for '/Volumes/Network_Drive/Documents/samples/XXXX.***': Operation not permitted"
Is there some way for the app too retain the directory permissions so that future file reads at permitted.
Thanks
Post not yet marked as solved
Thanks, I figured that it might be a bug and have submitted a report via FeedbackAssistant (#FB9079551) and raised a DTI where they told me you had responded here :-)
Yes I have existing application with existing archives. Note that the attachments are PDF documents or images the user may have pasted in to the text view.
Not sure whether it would be possible to convert the file attachments to data without loosing some file details but I suspect so.
Anyway thanks for the great response. I don't think I have ever had a useful response from anyone from Apple on these forums before - great to see such good support these days. ***** (that's 5 stars!)
Regards
Post not yet marked as solved
This might have nothing to do with your issue but we experienced the same problem with our background reporting threads where they suddenly took forever to run. We solved that by setting the thread or queue priority to be user interactive (or something like that). Sorry I don't have the details in front of me.
I have no idea if you can do the same with the drawing threads for CATiledLayer - or whether this the issue but thought it was worth mentioning.
Let us know if you find the solution.
