To fix this, first modify the “elements” array to be a NSMutableArray instead of just NSArray.
Then, modify the setText: selector to read the following:
- (void)setText:(NSString *)value {
[elements release];

elements = [NSMutableArray array];
for (NSString *element in [value componentsSeparatedByString:@" "])
{
if ([element rangeOfString:@"\n"].location != NSNotFound)
{
NSArray *temp = [element componentsSeparatedByString:@"\n"];
for (NSString *tempEl in temp)
{
[elements addObject: ([tempEl length] == 1 ? @”\n” : tempEl)];
}
}
else
{
[elements addObject:element];
}
}

[elements retain];

[self setNeedsLayout];
}

In the layoutSubviews override, after the elementSize and controlSize are calculated, replace the if statement to take into account that a new line will have a width of zero, and to instruct the rendering to increase the y component of the location

if(elementSize.height > controlSize.height || elementSize.width == 0) {
position.y += controlSize.height;
position.x = 0.0;
}

By now everything works pretty well, but there will be an extra space in front of the first words after the new line, so you have to modify the spaceSize towards the end of the loop to

CGSize spaceSize = elementSize.width == 0 ? (CGSize) {0,0} : [@" " sizeWithFont:styleFont];
position.x += elementSize.width + spaceSize.width;

That’s about all. Otherwise, great class, thanks

Thanks for the info, it’s interesting that you lose the edit controls with the simple two-line trick, however we’ve only ever used it in ‘display’ mode.

Thanks for taking the time to post your experience for others to read.

Simon.

The simple block described in this post only partially worked for me:
[myTableView beginUpdates];
[myTableView endUpdates];

My table is in a sort of permanent Edit mode so that it can show re-order controls, which means I have to have a sort of custom Edit button that expands the cells and shows the deletion controls next to each one (and hides them again when the user taps the button again, when it’s displaying Done instead of Edit).

The regular call I was doing to [tableView reloadData] at the end of my custom Edit button’s responder wasn’t animating the change, which is why I went searching and found Simon’s post on this site in the first place. For some reason, while reloadData was properly displaying the table with the enlarged cells and deletion controls, it wasn’t creating any sort of transition to it – very jarring and un-iphone-like!

After I implemented Simon’s block, I had animation… but no deletion controls! Evidently, the beginUpdates/endUpdates block successfully animates changes to cell heights, but because my action isn’t part of the normal series of steps that requires animations (steps like didSelectRowAtIndexPath or the wholesale reloadData), it wouldn’t call the method triggering the display of deletion controls, ie:

– (UITableViewCellEditingStyle)tableView:(UITableView *)tableView editingStyleForRowAtIndexPath:(NSIndexPath *)indexPath

I’m pretty sure it’s because I’m trying to animate a change to the row height for my entire table in response to a “custom event” (eg tapping a button outside the table itself that also isn’t the standard Edit or + button, instead of a row inside the table), in combination with the fact that my table is already in Edit mode, that the beginUpdates/endUpdates solution isn’t sufficient. My presumption is that a method like didSelectRowAtIndexPath already sets up (or “primes”) the table for animation just for the selection part, although I’m not experienced enough to explain it. And with [tableView reloadData] refusing to animate, I thought I had run out of options. It was in consulting the Apple developer docs that I found something that finally worked – a happy medium, if you will, that married what I needed of reloadData and beginUpates/endUpdates:

[tableView reloadSections:sectionsForReload withRowAnimation:UITableViewRowAnimationAutomatic];

Since my table was just one section, I defined sectionsForReload as:
NSIndexSet *sectionsForReload = [[NSIndexSet alloc] initWithIndex:0];

This can also be done on a row-by-row basis. I would of course be curious to know what other experiences people have had in this particular situation!