On 13 Aug 2014, at 23:40, Ken Thomases wrote:
>
> You have to issue the -willChange… _before_ the property has changed. That's
> because that's KVO's only opportunity to get the value that's about to become
> "old" and remove its observations for the properties of that old object.
>
> So, t
On 13 Aug 2014, at 23:41, Quincey Morris
wrote:
> On Aug 13, 2014, at 14:53 , Jonathan Mitchell wrote:
>
>> At one point i need to invoke a manual KVO notification like so:
>>
>> [submission willChangeValueForKey:@“status”];
>> [submission didChangeValueForKey:@“status”];
>>
>> This raises
On Aug 13, 2014, at 14:53 , Jonathan Mitchell wrote:
> At one point i need to invoke a manual KVO notification like so:
>
> [submission willChangeValueForKey:@“status”];
> [submission didChangeValueForKey:@“status”];
>
> This raises like so:
>
> Terminating app due to uncaught exception 'NSInt
On Aug 13, 2014, at 4:53 PM, Jonathan Mitchell wrote:
> I have a key path like so which is observed:
>
> submission.status.name
>
> At one point i need to invoke a manual KVO notification like so:
>
> [submission willChangeValueForKey:@“status”];
> [submission didChangeValueForKey:@“status”];
Have you implemented +automaticallyNotifiesObserversForKey: and returned NO for
“status” ?
On Aug 13, 2014, at 2:53 PM, Jonathan Mitchell wrote:
> I have a key path like so which is observed:
>
> submission.status.name
>
> At one point i need to invoke a manual KVO notification like so:
>
>
I have a key path like so which is observed:
submission.status.name
At one point i need to invoke a manual KVO notification like so:
[submission willChangeValueForKey:@“status”];
[submission didChangeValueForKey:@“status”];
This raises like so:
Terminating app due to uncaught exception 'NSInte
