Handling unpresented files with NSDocument

Hey everyone. I’m writing a document-based audio-editor for macOS and have a problem with managing the user's audio files. The app uses CoreAudio exclusively for everything audio related including reading and writing audio files to/from disk. When the user imports an audio file into the applic

NSCollectionViewItem lifecycle

Hi all, I’m experiencing what appears to be some sort of a memory leak with my use of NSCollectionView. I’ve figured out that this problem has actually always been happening ever since I added this particular collection view to the project; I just never noticed because the memory footprint of

Re: Handling unpresented files with NSDocument

> On 2016 Aug 03, at 07:56, maximilian.schm...@mto.io wrote: > > can CoreData solve this? If you are using Core Data for other reasons, then you should consider using BSManagedDocument, and you should read the discussion of saving and copying “additional content”, (which would be your audio fi

Re: Handling unpresented files with NSDocument

On Aug 3, 2016, at 07:56 , maximilian.schm...@mto.io wrote: > > Is it possible for the NSDocument to know about the audio files in it’s > package folder and handle them like they belong to it without wholly > representing them in the model? I don’t believe there’s any good solution based on a u

Re: Justification of collection cells in sections

So, does anyone know if the current behavior I mentioned is a bug? Is the behavior of Flow Layout documented? Should I file a bug with Apple? Also, what would be some quick ways to modify the flow layout behavior to handle this case with one item per section? Doug Hill > On Aug 2, 2016, at 6:1

Re: Justification of collection cells in sections

I remain a non-expert on this topic, but my assumption has always been that the current “look” is by design. Ugly, but by design. “Equally distribute cells across the row” could be taken to mean that in the case of one cell, it belongs in the middle… [shrug] This is some of the first Cocoa code I

Re: Emailing from a daemon process

Could use a simple Perl script… quick easy and nasty… #!/usr/bin/perl # … # from an old online sales system that is still operational ... { open(MAIL2,"|/usr/sbin/sendmail -t -f nobody") || &mydie("Hmmm, a nasty horrible server error

Re: Emailing from a daemon process

> On Jul 7, 2016, at 6:56 PM, Bruce Stephens wrote: > > Could use a simple Perl script… quick easy and nasty… We already spent many messages dissecting why simply invoking sendmail doesn’t work. > Works!!! It might work on your machine, because you’ve configured Postfix to route mail proper

Re: Handling unpresented files with NSDocument

> On Aug 3, 2016, at 11:51 PM, Quincey Morris > wrote: > > On Aug 3, 2016, at 07:56 , maximilian.schm...@mto.io > wrote: >> >> Is it possible for the NSDocument to know about the audio files in it’s >> package folder and handle them like they belong to it w

Re: Handling unpresented files with NSDocument

> On Aug 3, 2016, at 11:04 PM, Jerome Krinock wrote: > > >> On 2016 Aug 03, at 07:56, maximilian.schm...@mto.io wrote: >> >> can CoreData solve this? > > If you are using Core Data for other reasons, then you should consider using > BSManagedDocument, and you should read the discussion of sa

Re: Handling unpresented files with NSDocument

On Aug 3, 2016, at 20:49 , maximilian.schm...@mto.io wrote: > > But when working in a team on a professional level (like I have for many > years), when the document is copied around many times from Mac to Mac, to and > from a shared server, the asset-management has to be as simple, transparent