On Feb 22, 2009, at 10:23 AM, Iceberg-Dev wrote:
If the notification center coalesced observers on registration, the
above would mean that the notification would no longer be sent.
If anObject is the same object in the 3 calls, this is probably
already the case if I am to believe the documen
On Feb 22, 2009, at 7:06 PM, Bill Bumgarner wrote:
On Feb 22, 2009, at 9:59 AM, Iceberg-Dev wrote:
[...]
The current behavior makes it possible to implement architectures
where a client could take "more action" for any given
notification by registering more than once. Not supporting this
On Feb 22, 2009, at 9:59 AM, Iceberg-Dev wrote:
Thanks for the pointer. It would be nice to have this explanation
available in the description of the
addObserver:selector:name:object: as it might be where one could
expect to find it. I filed an enhancement suggestion.
But then it would hav
On Feb 22, 2009, at 6:39 PM, Bill Bumgarner wrote:
On Feb 22, 2009, at 8:59 AM, Iceberg-Dev wrote:
On Feb 22, 2009, at 1:37 AM, Michael Ash wrote:
On Sat, Feb 21, 2009 at 6:06 PM, Iceberg-Dev
wrote:
I just discovered something recently. If you register an
observer with the
same name/objec
On Feb 22, 2009, at 8:59 AM, Iceberg-Dev wrote:
On Feb 22, 2009, at 1:37 AM, Michael Ash wrote:
On Sat, Feb 21, 2009 at 6:06 PM, Iceberg-Dev
wrote:
I just discovered something recently. If you register an observer
with the
same name/object/selector twice, you get the notification twice
whe
On Feb 22, 2009, at 1:37 AM, Michael Ash wrote:
On Sat, Feb 21, 2009 at 6:06 PM, Iceberg-Dev
wrote:
I just discovered something recently. If you register an observer
with the
same name/object/selector twice, you get the notification twice
when you
post it.
Isn't the NSNotificationCenter
Le 22 févr. 09 à 10:52, Frédéric Testuz a écrit :
Le 22 févr. 09 à 00:06, Iceberg-Dev a écrit :
I just discovered something recently. If you register an observer
with the same name/object/selector twice, you get the notification
twice when you post it.
Isn't the NSNotificationCenter supp
Le 22 févr. 09 à 00:06, Iceberg-Dev a écrit :
I just discovered something recently. If you register an observer
with the same name/object/selector twice, you get the notification
twice when you post it.
Isn't the NSNotificationCenter supposed to prevent this?
Notifications post via a NSNo
On Sat, Feb 21, 2009 at 6:06 PM, Iceberg-Dev wrote:
> I just discovered something recently. If you register an observer with the
> same name/object/selector twice, you get the notification twice when you
> post it.
>
> Isn't the NSNotificationCenter supposed to prevent this?
Why, is there some pl
I just discovered something recently. If you register an observer
with the same name/object/selector twice, you get the notification
twice when you post it.
Isn't the NSNotificationCenter supposed to prevent this?
___
Cocoa-dev mailing list (Cocoa-
10 matches
Mail list logo
