Thanks. I’ll let you know when I can try it out later tonight.
> On Sep 8, 2014, at 3:40 PM, Jerry Krinock wrote:
>
>
> On 2014 Sep 08, at 11:09, Alex Kac wrote:
>
>> Is there a better way?
>
> How about redirecting standardUserDefaults, by sending it -addSuiteNamed: and
> -removedSuiteName
On 2014 Sep 08, at 11:09, Alex Kac wrote:
> Is there a better way?
How about redirecting standardUserDefaults, by sending it -addSuiteNamed: and
-removedSuiteNamed: during launching?
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do
Hi Alex. Xcode will also complain if you don’t call super. You must call super
and assign it to self…but then it seems that you are free to re-assign self -
which I kinda get - the parent class might be doing important stuff in
super…maybe there’s a more primitive init method I can override.
Id
Stupid question, but what happens if you don't assign the first self to the
result of the call, but just call [super initWithCoder: coder]?
Do you need the result of that call, since you immediately override it?
Sent from my iPad
On Sep 8, 2014, at 2:09 PM, Alex Kac wrote:
> This feels like
This feels like there should be an easy answer...
We are no longer using standardUserDefaults since we want to someday offer a
widget for our app that will require accessing our app's preferences..so we're
using NSUserDefaults with a custom suiteName.
*The question is*: in the NIBs for our P
