Hey Sean,
Thank you! Though this didn't quite work. I'm getting an error response in
the code telling me No visible @interface for 'NSFileManger' declares the
selector 'createDirectoryAtURL:attributes'. Included in this message is the
code im playing with,
On 26/11/2012, at 9:44 AM, Tom Miller t...@pxlc.me wrote:
Thank you! Though this didn't quite work. I'm getting an error response in
the code telling me No visible @interface for 'NSFileManger' declares the
selector 'createDirectoryAtURL:attributes'. Included in this message is the
code im
On Wed, 21 Nov 2012 18:17:26 -0500, Tom Miller said:
Sorry my bad! The warning states 'createDirectoryAtPath:attributes:' is
depreciated. I was able to get rid of that window warning once the app
launched, miss spelled something in my code. Though I'm still unable to
save the imputed text to the
On 23/11/2012, at 2:58 AM, Sean McBride s...@rogue-research.com wrote:
Most path-based and non-NSError-returning file APIs are deprecated
Is that documented anywhere? All I can see is this in the NSFileManager
reference:
The NSFileManager class supports both the NSURL and NSString classes as
On Fri, 23 Nov 2012 09:14:51 +1100, Shane Stanley said:
Most path-based and non-NSError-returning file APIs are deprecated
Is that documented anywhere?
Not sure if it's called out in black and white, but you just have to browse the
headers to see that all the newer file-related APIs use NSURL
I'm working with some code that accesses a data model in Xcode. String data
is written to an xml file in the app (Mac) and displayed in a list.
The inputted text is saved as body text and title. The app compiles but I
receive a warning upon launch,
*The managed object model version used to open
On 21 Nov 2012, at 21:16, Tom Miller t...@pxlc.me wrote:
I receive a warning in Xcode about this line of code dealing with the file
manager,
fileManager = [NSFileManager defaultManager];
applicationSupportFolder = [self applicationSupportFolder];
if ( 