• 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: delayed read-only bindings (suggestions/hints) ?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: delayed read-only bindings (suggestions/hints) ?


  • Subject: Re: delayed read-only bindings (suggestions/hints) ?
  • From: Nicolas Berloquin <email@hidden>
  • Date: Wed, 21 Apr 2004 22:34:45 +0200

ok I see what you mean, but in this case, what if say the last change
happens between "fire" time, then there is no
change for a while ? the latest value never gets updated.

But besides that, wouldn't it be more convenient to have a derived
class from say NSArrayController that does the buffering ?
This way, you wouldn't have to touch anything to your existing code ?

the doc says:
In the context of the controller layer, view objects observe controller
objects that in turn observe model objects. When the state of an object
changes, key-value observing provides details of the changes to
observers of that object. It is then the responsibility of the objects
observers to decide what to do with that information.

so the arrayController, for example would be a good target for that.
But what methods should be derived ?

(or am I completely off ?)

On 21 avr. 04, at 22:13, Scott Anguish wrote:

>
> On Apr 21, 2004, at 4:01 PM, Allan Odgaard wrote:
>
>> On 21. Apr 2004, at 21:43, Scott Anguish wrote:
>>
>>>>> if you turned off automatic KVO for that class [...] only send the
>>>>> did/will change notifications once per second.
>>>> Ehm... should the willChange... not be sent *before* changing the
>>>> value? [...]
>>> sure.. I didn't mean use did then will, rather just send them only
>>> sporadically.
>>
>> Sorry, but this I do not understand. Do you mean that he should
>> buffer the changes and then (once a second) send the willChange,
>> apply all the changes, and then the didChange?
>>
>>
>
> Well, not really.
>
> implementing his own accessor, that for most changes just doesn't
> call the will/did change methods. Only call those periodically.
>
> the values will be updated in the model, but the tableview will only
> be updated when the change methods are called.
>
> does that clarify it?
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.


References: 
 >delayed read-only bindings (suggestions/hints) ? (From: Nicolas Berloquin <email@hidden>)
 >Re: delayed read-only bindings (suggestions/hints) ? (From: Scott Anguish <email@hidden>)
 >Re: delayed read-only bindings (suggestions/hints) ? (From: Allan Odgaard <email@hidden>)
 >Re: delayed read-only bindings (suggestions/hints) ? (From: Scott Anguish <email@hidden>)
 >Re: delayed read-only bindings (suggestions/hints) ? (From: Allan Odgaard <email@hidden>)
 >Re: delayed read-only bindings (suggestions/hints) ? (From: Scott Anguish <email@hidden>)

  • Prev by Date: CFStringRef == NSString* ?
  • Next by Date: Re: Slightly OT: anybody familiar with USB?
  • Previous by thread: Re: delayed read-only bindings (suggestions/hints) ?
  • Next by thread: Re: delayed read-only bindings (suggestions/hints) ?
  • Index(es):
    • Date
    • Thread