Console.app told me: default 22:57:28.157905+0700 ReportCrash Saved crash report for chronyd[15863] version 0 to chronyd_2019-12-14-225728_Spinat.crash But I cannot find this. Where should I

I’m looking for a macOS developer to join our team in Northern NJ. This is for mid-level candidates or higher. Candidates must be well versed or fluent in the following: Objective-C/C SQL

I just thought you might know. It's too complex for me to rejigger it all just to find that answer, and I have it working now, so I don't care. :) -- Steve Mills Drummer, Mac geek

I’m looking for a macOS developer to join our team in Northern NJ. This is for mid-level candidates or higher. Candidates must be well versed or fluent in the following: Objective-C/C SQL

I suspect you can answer that quicker than me. -- Shane Stanley <sstanley@...> <www.macosxautomation.com/applescript/apps/>, <latenightsw.com>

Does that give you the multiple images thing where different destinations can rearrange the images in stacks, grids, or whatever? My drag source is a collection view or a table view, so the initial

Maybe I'm missing something, but can't you just use this: [[NSPasteboard generalPasteboard] clearContents]; [[NSPasteboard generalPasteboard] writeObjects:@[url]]; -- Shane Stanley

After just trying all kinds of random crap, I got it to work. Turns out, if you call [url pasteboardPropertyListForType:NSPasteboardTypeFileURL], you can't use that with [pbItem setPropertyList:thing

OK, so after "modernizing" my app to add multiple drag items (flavor NSPasteboardTypeFileURL) to the drag clipboard instead of just one with multiple flavors (NSFilenamesPboardType and

Thanks for this. I ended up pre- and post-processing entities that aren't normally handled by the parser or the delegate in other places, because I simply want them to persist. Yeah, NSXMLParser and

IRC, NSXMLParser is pretty vanilla, and back in the day it was recommended to use an xml parsing library directly rather than NSXMLParser if you have to work with anything except basic XML. Does not

I also wonder (thanks to the lack of documentation) if I should be supplying some standard urls in the allowedExternalEntityURLs property of the NSXMLParser. Would that cause the parser to

Same error. Thanks for the suggestion. -- Steve Mills Drummer, Mac geek

Have you tried returning a full XML entity, e.g. "<string>&#xa0</string>"? That would be my next experiment... -- Glenn L. Austin, Computer Wizard and Race Car Driver

What is the expected value of the returned NSData supposed to be for this method? The docs says "An NSData object that contains the resolution of the given external entity." To me, that means that for

Ugh - I don't have a whole lot of experience with CoreData, but it does add a whole lot of possible failure modes. It's tough that you can't reproduce the issue locally - any chance the customer will

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00006db9f91b0e58 Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Segmentation fault:

What's the actual cause of the crash? A segmentation fault (SIGSEGV) or some other memory error could be caused by you corrupting memory, handing NSDocumentController a bad object somehow, or some

A customer sent a crashlog that clearly shows Apple's code is what's crashing on 10.14.6. There's no way I can reproduce it. So what can I do? Just submit a bug to Apple with the crashlog (although

Is it possible to set up an AVAudioEngine and friends so I could feed it a sequence of MIDI notes and have it play that sequence, using an AVAudioSourceNode as the sound source? The AVAudioSourceNode