Thanks Luke and Quincey, I think understand better now. Seems like
'heightForRowAtIndexPath' is the right thing to do. I have different table rows
so configuring a fixed row height in IB (which is possible) is not an option
for me.
And 'yes' I'm talking about UITableView. ;)
Regards,
Tino
Am
On May 29, 2010, at 09:48, Luke the Hiesterman wrote:
> I realized we're talking about different things. My mind when instantly to
> UITableView and I didn't realize we were talking about NSTableView. I can
> only speak for UITableView :)
Well, you made the correct assumption. I didn't read the
I realized we're talking about different things. My mind when instantly to
UITableView and I didn't realize we were talking about NSTableView. I can only
speak for UITableView :)
Luke
On May 29, 2010, at 9:45 AM, Quincey Morris wrote:
> On May 29, 2010, at 08:56, Luke Hiesterman wrote:
>
>> I
On May 29, 2010, at 08:56, Luke Hiesterman wrote:
> I'm not sure why you're trying to separate the ideas of row and cell height.
> I don't think there's any reason why you should ever attempt to have a cell
> whose height is different from the height returned in heightForRowAtIndexPath.
Well, t
I'm not sure why you're trying to separate the ideas of row and cell height. I
don't think there's any reason why you should ever attempt to have a cell whose
height is different from the height returned in heightForRowAtIndexPath. In
fact, you shouldn't even be setting cell frames yourself. The
On May 28, 2010, at 23:39, Tino Rachui wrote:
> I've created a table view cell in interface builder with a custom height.
> However when I load and use that kind of cell at runtime it disregards my
> custom height. I have to use 'heightForRowAtIndexPath' to set the desired
> cell height. Is the
