How to calculate height of cell to contain text?

[Duncan C]

I am creating a UITableView that will be used to display cells that contain, among other things, a UITextView. (or possibly a UILabel)

The contents of the text view will vary from cell to cell. I want to make each cell tall enough to display the text in it's text view.

How do I calculate how tall my text field needs to be in order to display the text I want to display? (at the current font and size for the view.)

[mnemonic_fx]

NSString *string = ...;

CGSize stringSize = [string sizeWithFont:[UIFont boldSystemFontOfSize:kTextFieldFontSize] constrainedToSize:CGSizeMake(320, 9999) lineBreakMode:UILineBreakModeWordWrap];

Then you could use the stringSize however you want, the key is in 9999 as a height.
You would rarely find any text view rect with more than 9999 as a height. Unless if it's an article or something.

Currently, I can not find any way to calculate it without constraint.

[LunarMoon]

This routine do not works very well, probably due to some bug.

The calculated frame size is not correct when you have letters that go below the baseline. The string aaaaa will be fine, but not aapqg, because qpg have pixels below the base line.

[Duncan C]

Originally Posted by LunarMoon

This routine do not works very well, probably due to some bug.

The calculated frame size is not correct when you have letters that go below the baseline. The string aaaaa will be fine, but not aapqg, because qpg have pixels below the base line.

Oh great.

What are the errors like? Does the frame size it gives you clip the descenders of the characters on the bottom row?

I haven't looked into fonts in Cocoa, but it should be possible to query the font for the leading value at the current size and style, and round the answer you get back up to the next multiple of the total font height (height + leading). Even simpler, you could just add myfont.descender to the height you get back from the call to sizeWithFont: constrainedToSize:.


Duncan C

[PhoneyDeveloper]

Typically you want table rows to be a minimum of 44 high. Also, I find I usually add some margin also. If LunarMoon is correct I've noticed this problem since I'm always adding at least 20 pixels to the height anyway.

[LunarMoon]

This is also my case. I am adding exactly 20 pixels too!!!! If you want to see the bug just add the text to the UITextView programatically as

[box setText: @"apqgbADF"];

and then use the code by mnemonic_fx

To see the full effect paint the box yellow before using the code or make it clip on the boundary. All letters with pixels below the baseline will be cut, i.e., it will clip the descenders of the characters on the bottom row.

I cannot believe Apple left behind something so simple and so basic as centering a &%$&#%$&% text vertically! We have to build 10,000 lines of code using sometimes buggy code to center a text on a box.

This remembers me the nightmare you have to pass to center a /&%%%#/ text horizontally and vertically (in all browsers) using CSS in HTML? What is wrong with these guys creating programming languages and standards? They build cars but always forgot to put the steering wheels.

[PhoneyDeveloper]

My tableviews have UILabels in them. So the bug you describe is with UITextView? I guess that's why I haven't seen it.

[LunarMoon]

yes, with UITextView.

[dicklacara]

Originally Posted by LunarMoon

I cannot believe Apple left behind something so simple and so basic as centering a &%$&#%$&% text vertically! We have to build 10,000 lines of code using sometimes buggy code to center a text on a box.

...this from the guys that created enough NSString methods to strangle a Clydesdale

Ahh... one must understand the Apple "mindset"...

1) The impossible... we deliver!
2) The difficult... we make easy!
3) The basic... we ignore!

from 30 years experience dealing with Apple

HTH

Dick

[LunarMoon]

unbelievable.... and BTW this Objective-C language oficially used to develop the applications is the most insane and complex language I ever used. I can understand the language without problems but I have sanity to see it very complex and not open to the everyone.

something like...

if (x == "string")

becomes

if ([x isEqualToString:@"string"])

or...

x = [10, 20, 30];

becomes

x = [[[NSMutableArray alloc] initWithObjects:
	   [[NSNumber alloc] initWithInteger:10],
	   [[NSNumber alloc] initWithInteger:20],
	   [[NSNumber alloc] initWithInteger:30],
	   nil] retain];

is insanity at its best... why easy things? what Apple has to gain? more developers? more users? pfuuuuu