9/2/08 11:04 AM, also sprach [EMAIL PROTECTED]:
>> Some other suggestions: storing the shared defaults and controller is really
>> just a waste of memory. They won't change across invocations.
>
>
> With the overhead of Objective C messaging, isn't it more efficient
> to obtain once and store th
> For what it's worth, the [sharedUserDefaultsController save:]
message is still
returning before performing the save, so if I send any other messages within
my savePrefs method, userDefaults will still contain the old value - I'm
beginning to wonder if this is a bug within NSUserDefaultsCont
9/2/08 2:37 AM, also sprach [EMAIL PROTECTED]:
> For what it's worth, the [sharedUserDefaultsController save:] message is still
> returning before performing the save, so if I send any other messages within
> my savePrefs method, userDefaults will still contain the old value - I'm
> beginning to w
I think I've fixed the the problem, thanks to an idea I had whilst reading
Oleg's "Bindings - newbie question" thread.
I've added a message within -init to bind my model's variable (theValue) to the
appropriate value (thevalue) within the standardUserDefaults dictionary
(myPrefs). Apologies fo
Apparently NSUserDefaults delays its saving until the next time
through the event loop, perhaps by using one of the
performSelector:afterDelay calls, or something like that. Is it
possible that this is what's causing your issues?
I ran into this problem when trying to save user defaults at
>> I've been playing around with bindings to NSUserDefaultsController in
a very simple app to test saving preferences, but the
[sharedUserDefaultsController save:self] method seems to return
immediately
without waiting for the save operation to complete.
The save does actually take place,
On Sun, Aug 31, 2008 at 12:13 PM, Mark Allan
<[EMAIL PROTECTED]> wrote:
For what it's worth, I also get these compiler warnings for the line with
[sharedUserDefaultsController save:]
warning: multiple methods named '-save:' found
warning: using '-(void)save:(id)sender'
warning: also found '
On Sun, Aug 31, 2008 at 12:13 PM, Mark Allan
<[EMAIL PROTECTED]> wrote:
> For what it's worth, I also get these compiler warnings for the line with
> [sharedUserDefaultsController save:]
>
> warning: multiple methods named '-save:' found
> warning: using '-(void)save:(id)sender'
> warning: also fou
8/31/08 4:11 PM, also sprach [EMAIL PROTECTED]:
>> I've been playing around with bindings to NSUserDefaultsController in
>>> a very simple app to test saving preferences, but the
>>> [sharedUserDefaultsController save:self] method seems to return immediately
>>> without waiting for the save operat
On 31 Aug 2008, at 17:25, Keary Suska <> wrote:
8/31/08 10:13 AM, also sprach:
I've been playing around with bindings to NSUserDefaultsController in
a very simple app to test saving preferences, but the
[sharedUserDefaultsController save:self] method seems to return
immediately without waiti
8/31/08 10:13 AM, also sprach [EMAIL PROTECTED]:
> I've been playing around with bindings to NSUserDefaultsController in
> a very simple app to test saving preferences, but the
> [sharedUserDefaultsController save:self] method seems to return
> immediately without waiting for the save operation to
Hi,
I've been playing around with bindings to NSUserDefaultsController in
a very simple app to test saving preferences, but the
[sharedUserDefaultsController save:self] method seems to return
immediately without waiting for the save operation to complete.
The save does actually take place, w
12 matches
Mail list logo
