Makes sense, but I would have a much bigger problem if it would be every
non-admin account I think. But yeah I need to fix my code and go from there.
I’ll let you guys know if I have problems after that thanks!
rc
On Dec 13, 2014, at 6:31 AM, Seth Willits s...@freaksw.com wrote:
On Dec
Rick C. rickcort...@gmail.com wrote:
I write an NSString and NSData object to my app’s .plist and of course read it
back when needed and this works fine 99% of the time. On occasion a user
reports some trouble to me and I ask for the .plist and find out that this
NSString/NSData object is
On Dec 10, 2014, at 11:05 PM, Rick C. rickcort...@gmail.com wrote:
Hi,
Digging deeper I find that most often the user has their home folder on a
different drive (external?) than the actual app. What would be the solution
to make sure these objects are written properly in this case?
On Dec 10, 2014, at 11:05 PM, Rick C. rickcort...@gmail.com wrote:
I write an NSString and NSData object to my app’s .plist and of course read
it back when needed and this works fine 99% of the time. On occasion a user
reports some trouble to me and I ask for the .plist and find out that
So I found some old code where I was using NSAppleScript with defaults write
ouch! :-) Sorry about that but curious why would this fail at times? Pretty
sure that switching it to the proper NSUserDefaults will work fine…
On Dec 11, 2014, at 10:24 PM, gweston gwes...@mac.com wrote:
Rick
Hi,
I write an NSString and NSData object to my app’s .plist and of course read it
back when needed and this works fine 99% of the time. On occasion a user
reports some trouble to me and I ask for the .plist and find out that this
NSString/NSData object is missing. Digging deeper I find that
