• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: observeValueForKeyPath:... called too often in macOS 12
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: observeValueForKeyPath:... called too often in macOS 12


  • Subject: Re: observeValueForKeyPath:... called too often in macOS 12
  • From: "Gerriet M. Denkmann" <email@hidden>
  • Date: Wed, 19 Oct 2016 11:43:09 +0700

> On 19 Oct 2016, at 09:55, Gary L. Wade <email@hidden> wrote:
>
> I have a thought.  Do you have a binding somewhere on a property in NSUserDefaults?

I just made a small test app: not document based, two TextFields bound to User Defaults Controller at values.TextField1, resp. …2.
Both observed via addObserver:forKeyPath:…

> Maybe your document is getting synchronised to iCloud and/or getting autosaved very often?

As far as I know, I am not using iCloud at all. Neither using auto save or anything.

If you (or anyone else) are interested, I can send you the test app project.

Kind regards,

Gerriet.


> These are things I’ve seen that can cause uncharacteristically often updates.
> --
> Gary L. Wade
> http://www.garywade.com/
>
>> On Oct 18, 2016, at 7:32 PM, Gerriet M. Denkmann <email@hidden> wrote:
>>
>>
>>> On 19 Oct 2016, at 02:00,Jerome Krinock <email@hidden>:
>>>
>>>> On 2016 Oct 14, at 23:08, Gerriet M. Denkmann <email@hidden> wrote:
>>>>
>>>> My app (macOS 12) observes a value in NSUserDefaults.  Starting with macOS 12 observeValueForKeyPath:… is called at the start of the program, although nothing has changed yet.  When the value actually changes, it is called twice.
>>>
>>> I just added some code to one of my apps, to test this.  It confirmed your observations, although I only tested in 10.12.
>>>
>>>> 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 added.
>>
>> Happens for me all the time. Never seen anything other than NSNull.
>>
>> 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.
>>
>>>
>>>> If indeed this behavior is new in 10.12, it certainly warrants a Bug Report.
>>
>> Ok, will do so.
>>
>> Kind regards,
>>
>> Gerriet.
>


_______________________________________________

Cocoa-dev mailing list (email@hidden)

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 email@hidden


References: 
 >Re: observeValueForKeyPath:... called too often in macOS 12 (From: "Gerriet M. Denkmann" <email@hidden>)
 >Re: observeValueForKeyPath:... called too often in macOS 12 (From: "Gary L. Wade" <email@hidden>)

  • Prev by Date: Re: inconsistencies in view renderings
  • Next by Date: Re: observeValueForKeyPath:... called too often in macOS 12
  • Previous by thread: Re: observeValueForKeyPath:... called too often in macOS 12
  • Next by thread: Re: observeValueForKeyPath:... called too often in macOS 12
  • Index(es):
    • Date
    • Thread