Why the frame of the UILabel in standard UITableViewCell is (0,0,0,0) and What's the Standard Size of UITableViewCell.textLabel? - objective-c

Question

I want to replace that with a webview so I can display html.
PO(cell.subviews);
PO(cell);
PO(cell.contentView.subviews);
The webview need to have the same frame with the frame of UITableViewCell.
This is what we got:
2013-01-31 12:37:35.204 BadgerNew[3888:c07] cell.subviews: (
"<UITableViewCellContentView: 0xa057140; frame = (0 0; 320 44); layer = <CALayer: 0xa057180>>"
)
2013-01-31 12:37:35.204 BadgerNew[3888:c07] cell: <UITableViewCell: 0xa0c37a0; frame = (0 0; 320 44); text = 'atm'; layer = <CALayer: 0xa0c8530>>
2013-01-31 12:37:35.205 BadgerNew[3888:c07] cell.contentView.subviews: (
"<UILabel: 0xa0d12a0; frame = (0 0; 0 0); text = 'atm'; clipsToBounds = YES; userInteractionEnabled = NO; layer = <CALayer: 0xa0571b0>>"
)
Moreover, to further confirm
po [cell textLabel]
(UILabel *) $1 = 0x0a0d12a0 <UILabel: 0xa0d12a0; frame = (0 0; 0 0); text = 'atm'; clipsToBounds = YES; userInteractionEnabled = NO; layer = <CALayer: 0xa0571b0>>
What is the final standard frame for normal UITableViewCell then?
I also did
-(void)layoutSubviews
{
PO(self);
PO(self.textLabel);
while (false);
}
and got
2013-02-01 09:36:02.048 BadgerNew[1436:c07] self.textLabel: <UILabel: 0x8923390; frame = (0 0; 0 0); clipsToBounds = YES; userInteractionEnabled = NO; layer = <CALayer: 0x89e8fc0>>
Doing it in
- (void)tableView:(UITableView *)tableView willDisplayCell:(UITableViewCell *)cell forRowAtIndexPath:(NSIndexPath *)indexPath {
while (false);
}
yield the same result
Then I did:
-(void)layoutSubviews
{
[super layoutSubviews];
PO(self);
PO(self.textLabel);
while (false);
}
Again, another 0 frame.

Answer 1

The frames of the subviews within a cell are set after -tableView:cellForRowAtIndexPath.
Make a subclass of UITableViewCell, it's really the best way of handling things like this. You can override -textLabel in your subclass and bend it to your will, or you can override -layoutSubviews and use -textLabel's frame then.
One final warning, mucking around with the internals of an object causes brittle code that could break at any revision of iOS.