Skip to main content

Why is an IBOutletCollection pointing to static cells from storyboard returning null?



I have defined this in code:







@property (nonatomic, weak) IBOutletCollection(UITableViewCell) NSSet * certaintyCells;







and synthesized. I made absolutely sure that this controller is used in story board, and connected three cells to this collection.





Next, in the didSelectRowAtIndexPath: method call, I added this code, with NSLog added for debugging:







NSLog(@"Certainty Cells: %@",certaintyCells);

for (UITableViewCell * cell in certaintyCells) {

[cell.textLabel setTextColor:[UIColor colorWithRed:0 green:0 blue:0 alpha:1]];

[cell setSelectionStyle:UITableViewCellSelectionStyleBlue];

}







The output is this:







Certainty Cells: (null)







And of course, behaviour expected does not happen.





Any ideas as to why this is happening? I did make sure that I am using static cells, and not dynamic prototypes. As a side note, these three cells are also connected to (working) IBOutlets of their own.





Thanks,


Comments

Popular posts from this blog

Why is this Javascript much *slower* than its jQuery equivalent?

I have a HTML list of about 500 items and a "filter" box above it. I started by using jQuery to filter the list when I typed a letter (timing code added later): $('#filter').keyup( function() { var jqStart = (new Date).getTime(); var search = $(this).val().toLowerCase(); var $list = $('ul.ablist > li'); $list.each( function() { if ( $(this).text().toLowerCase().indexOf(search) === -1 ) $(this).hide(); else $(this).show(); } ); console.log('Time: ' + ((new Date).getTime() - jqStart)); } ); However, there was a couple of seconds delay after typing each letter (particularly the first letter). So I thought it may be slightly quicker if I used plain Javascript (I read recently that jQuery's each function is particularly slow). Here's my JS equivalent: document.getElementById('filter').addEventListener( 'keyup', function () { var jsStart = (new Date).getTime()...