Keeping the list server busy while everyone else seem to have better things to
do...
Is there an magic trick to get the framework to actually call NSDocument's
- (BOOL)canAsynchronouslyWriteToURL:(NSURL *)url ofType:(NSString *)typeName
forSaveOperation:(NSSaveOperationType)saveOperation
DeprecatedOn 6/10/12 7:21 PM, Markus Spoettl wrote:
Keeping the list server busy while everyone else seem to have better things to
do...
Is there an magic trick to get the framework to actually call NSDocument's
- (BOOL)canAsynchronouslyWriteToURL:(NSURL *)url ofType:(NSString *)typeName
On 6/10/12 7:45 PM, Markus Spoettl wrote:
Well, it suddenly started working and the reason is that apparently you need to
have
-saveToURL:ofType:forSaveOperation:completionHandler:
overwritten. If you don't you just don't get to use background writing.
Overwriting this method does the trick.
On Jun 10, 2012, at 1:45 PM, Markus Spoettl wrote:
DeprecatedOn 6/10/12 7:21 PM, Markus Spoettl wrote:
Keeping the list server busy while everyone else seem to have better things
to
do...
Is there an magic trick to get the framework to actually call NSDocument's
-
On 6/10/12 9:21 PM, Alex Zavatone wrote:
This is one of the joys of Mac development I've seen. Class methods are
called that you never know about and you have to override stuff that you
never knew were parts of the class, let alone are even called.
To be fair it is documented, just not were I
On 10 Jun 2012, at 10:45, Markus Spoettl wrote:
DeprecatedOn 6/10/12 7:21 PM, Markus Spoettl wrote:
Keeping the list server busy while everyone else seem to have better things
to
do...
Is there an magic trick to get the framework to actually call NSDocument's
-