Observing changes to GVUserDefaults property values about gvuserdefaults

[kevinrenskers]

All the properties are of course stored in NSUserDefaults so all normal observing patterns simply work. That said, having a dead easy, block based change notification system would be cool.

On 18 Dec 2013, at 22:26, Jonathan Sibley [email protected] wrote:

As far as I can tell, there is no support for observing property value changes via NSNotificationCenter or KVO. What are your thoughts on the prospect of this feature?

—
Reply to this email directly or view it on GitHub.

[sibljon]

AFAIK, observing NSUserDefaultsDidChangeNotification is the best way to observe NSUserDefaults, and it doesn't provide any information about specific updates. That's the main disadvantage.

I think a light-weight (and small code foot print) solution would be calling willChangeValueForKey: and didChangeValueForKey: when GVUserDefaults setters are used. However, these two calls need to be made in every single GVUserDefaults generic setter (i.e. doubleSetter, objectSetter, etc), right? Or can you think of a more centralized place to make the KVO calls?

[kevinrenskers]

Back from my vacation, I'll look into this soon.

[kevinrenskers]

As far as I can see, this already works fine without any code changes.

- (void)viewDidLoad {
    [super viewDidLoad];
    [[GVUserDefaults standardUserDefaults] addObserver:self forKeyPath:@"userName" options:NSKeyValueObservingOptionNew context:nil];
    [GVUserDefaults standardUserDefaults].userName = @"Test";
}

- (void)observeValueForKeyPath:(NSString *)keyPath ofObject:(id)object change:(NSDictionary *)change context:(void *)context {
    NSLog(@"keyPath: %@", keyPath);
}

[sibljon]

Interesting! I apologize for not having tested it... apparently my understanding of the implementation wasn't correct! Thanks for following up, and I hope you had a nice vacation.

[sibljon]

Just to follow up: KVO on GVUserDefaults is working perfectly in my testing. —
Sent from Mailbox for iPhone

On Tue, Jan 14, 2014 at 6:15 AM, Kevin Renskers [email protected]
wrote:

Closed #10.

Reply to this email directly or view it on GitHub:
#10

[kevinrenskers]

Awesome :)