Skip to main content

returning UIImage from block



I have the following code:







- (UIImage *) getPublisherLogo

{

//check the cache if the logo already exists

NSString * imageUrl = [NSString stringWithFormat:@"%@/%@&image_type=icon", self.baseUrl, self.imageUrl_];





ASIHTTPRequest * imageRequest = [ASIHTTPRequest requestWithURL:[NSURL URLWithString:imageUrl]];

[imageRequest setTimeOutSeconds:30.0];

[imageRequest setDownloadCache:[ASIDownloadCache sharedCache]];

[imageRequest setCacheStoragePolicy:ASICachePermanentlyCacheStoragePolicy];

[imageRequest setCachePolicy:ASIAskServerIfModifiedWhenStaleCachePolicy|ASIFallbackToCacheIfLoadFailsCachePolicy];

[imageRequest setCompletionBlock:^(void){





UIImage *img = [UIImage imageWithData:[imageRequest responseData] ];

if (img){

return img;

}

}];



[imageRequest setFailedBlock:^(void){

NSLog(@"Error in pulling image for publisher %@", [[imageRequest error] userInfo]);

}];



[imageRequest startAsynchronous];

}

}







The issue is that the return value/UIImage is returned at a block. How do I avoid this?


Comments

  1. You're unable to return anything from the completion block because it's returned void.

    You'll probably need to create a new method like setLogo:(UIImage *)image on the object that's expecting the image to be set, and call that method from within the completion block.

    ReplyDelete
  2. You can place your img pointer outside the block and declare it __BLOCK and use it as a closure. But you really need to be asking yourself what do you plan to do with img, bearing in mind the call is made asynchronously. I would imagine you should make another call in the block to another method and pass in the populated image as a parameter.

    ReplyDelete
  3. For getting an object from the ASIHttpRequest response, I use notifications.

    For example, in the calling viewController

    - (void)viewDidLoad {
    // Subscribe notifications
    [[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(onGetPhoto:) name:@"getPhotoNotification" object:nil];
    }

    - (void)viewDidUnload {
    [super viewDidUnload];
    // Unsubscribe from notifications
    [[NSNotificationCenter defaultCenter] removeObserver:self name:@"getPhotoNotification" object:nil];
    }

    - (void)onGetPhoto:(NSNotification *)notification {
    ...
    }


    in your completion block

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


    With your photo in userInfo.

    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