Skip to main content

how to use the object property of NSNotificationcenter


Could somebody please show me how to use the object property on NSNotifcationCenter. I want to be able to use it to pass an integer value to my selector method.



This is how I have set up the notification listener in my UI View. Seeing as I want an integer value to be passed I'm not sure what to replace nil with.




[[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(receiveEvent:) name:@"myevent" object:nil];


- (void)receiveEvent:(NSNotification *)notification {
// handle event

NSLog(@"got event %@", notification);
}



I dispatch the notification from another class like this. The function is passed a variable named index. It's this value that I want to somehow fire off with the notification.




-(void) disptachFunction:(int) index

{


int pass= (int)index;


[[NSNotificationCenter defaultCenter] postNotificationName:@"myevent" object:pass];
//[[NSNotificationCenter defaultCenter] postNotificationName:<#(NSString *)aName#> object:<#(id)anObject#>



}


Source: Tips4allCCNA FINAL EXAM

Comments

  1. The object parameter represents the sender of the notification, which is usually self.

    If you wish to pass along extra information, you need to use the NSNotificationCenter method postNotificationName:object:userInfo:, which takes an arbitrary dictionary of values (that you are free to define). The contents needs to be actual NSObject instances, not an integral type such as an integer, so you need to wrap the integer values with NSNumber objects.

    NSDictionary* dict = [NSDictionary dictionaryWithObject:
    [NSNumber numberWithInt:index]
    forKey:@"index"];

    [[NSNotificationCenter defaultCenter] postNotificationName:@"myevent"
    object:self
    userInfo:dict];

    ReplyDelete
  2. The object property is not appropriate for that. Instead you want to use the userinfo parameter:

    + (id)notificationWithName:(NSString *)aName
    object:(id)anObject
    userInfo:(NSDictionary *)userInfo


    userInfo is, as you can see, an NSDictionary specifically for sending information along with the notification.

    Your dispatchFunction method would instead be something like this:

    - (void) disptachFunction:(int) index {
    NSDictionary *userInfo = [NSDictionary dictionaryWithObject:[NSNumber numberWithInt:index] forKey:@"pass"];
    [[NSNotificationCenter defaultCenter] postNotificationName:@"myevent" object:nil userInfo:userInfo];
    }


    Your receiveEvent method would be something like this:

    - (void)receiveEvent:(NSNotification *)notification {
    int pass = [[[notification userInfo] valueForKey:@"pass"] intValue];
    }

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex