> On 2016 Oct 18, at 19:32, Gerriet M. Denkmann <g...@mdenkmann.de> wrote:
>> On 19 Oct 2016, at 02:00,Jerome Krinock <je...@ieee.org>:
>>> On 2016 Oct 14, at 23:08, Gerriet M. Denkmann <g...@mdenkmann.de> wrote:
>>> Also: NSKeyValueObservingOptionNew or NSKeyValueObservingOptionOld just
>>> return NSNull instead of old or new values.
>> That only happens during that first spurious call, when the observer is
> Happens for me all the time. Never seen anything other than NSNull.
Well, then there is something weird in your app, or in mine. I would bet on
yours, because if such change notifications were broken in 10.12, thousands of
apps would not work. Create a small demo project and try to reproduce.
> Current work-around: just ignore every second notification (i.e. ginore 1.,
> 3rd, 5th etc.).
> Not a very good solution, rather bound to break sooner or later. But okay for
> the time being.
“Not a very good solution”, indeed. If I understand you correctly, if you ran
your app in 10.11 with this “solution”, it wouldn’t work. The workaround that
I suggested (filtering for substantive changes), you know, at least it has a
logical basis, and if Apple changes this undocument behavior back to the old
undocumented behavior, it should still work.
Cocoa-dev mailing list (Cocoafirstname.lastname@example.org)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to arch...@mail-archive.com