On Jan 14, 2016, at 4:38 PM, Alex Kac wrote:
>
> I have a NIB with two views that I want to use depending on circumstances. I
> call one “weatherCell” and one “weatherCellNarrow”.
>
> I register it like this:
>
> - (NSString*)identifierForWeatherCell {
> return _narrowView ? @"weatherCe
On Jan 14, 2016, at 15:09 , Alex Kac wrote:
>
> Actually there is - the identifier. You set the NIB *and* the identifier.
Now that I’ve had time, I think I remember doing exactly this sometime in the
past. How soon we forget.
> And I was able to make it work right after I sent the email (isn
Actually there is - the identifier. You set the NIB *and* the identifier. And
I was able to make it work right after I sent the email (isn’t that how it is
always?) It seems that my “isNarrow” property wasn’t being set by the time the
view was loading where we were initializing it. I wasn’t abl
On Jan 14, 2016, at 14:38 , Alex Kac wrote:
>
> I can’t seem to get a good answer to if this should work or not (having
> multiple cellViews in one NIB).
No. There are 2 top level objects in your nib, but there’s nothing that tells
the table view machinery which one to use. (Normally, you’d u
I have a NIB with two views that I want to use depending on circumstances. I
call one “weatherCell” and one “weatherCellNarrow”.
I register it like this:
- (NSString*)identifierForWeatherCell {
return _narrowView ? @"weatherCellNarrow":@"weatherCell";
}
nib = [[NSNib alloc] i
