StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8779949
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-01-08T18:14:49.077
FavoriteCount
0
LastActivityDate
2012-01-09T12:56:34.810
LastEditDate
2012-01-09T12:56:34.810
LastEditorUserId
1127396
OwnerUserId
1127396
ParentId
8779220
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Yes, there is a side effect I can think of. Let me explain it. The method you talk about was actually defined in NSNotification.h as below: <ul> <li>(void)postNotificationName:(NSString *)notificationName object:(id)notificationSender</li> </ul> The first parameter notificationName stands for the name of the notification. The second parameter notificationSender stands for the object posting the notification. Yes, any object can be a notification sender, even nil can be. In terms of observering the notification(to became a observer of a specific notification), we got to know another method defined in NSNotification: <ul> <li>(void)addObserver:(id)notificationObserver selector:(SEL)notificationSelector name:(NSString *)notificationName object:(id)notificationSender</li> </ul> As you can see, the last parameter is notificationSender(the object whose notifications the observer wants to receive). So right now, the side effect is apparently. Let me explain it in detail. There are three controllers A, B, C.for example. The controller A post a notification helloEveryone. The controller B also post a notification helloEveryone. In C controller, if you place a statement like below: [[[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(helloEveryOne) name:@"helloEveryone" object:nil] Then you will receive two helloEveryone from controller A and controller B. if you place a statement like this: [[[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(helloEveryOne) name:@"helloEveryone" object:controllerA] Then you will receive only one helloEveryone from controller A. The self surely is not a nil notification sender as long as it can post a notification, but use another object as a notification sender, may be it is a nil object. And the observer's behave is different in terms of that whether notification sender is nil or not.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PONSNotification: does the object property have to be self?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USThomasTsang
UserOwnerUserId
1. USThomasTsang
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.