Per the release notes, your UITableViewDelegate MUST now return 0.0 from tableView:heightForHeaderInSection.
Per the release notes, your UITableViewDelegate MUST now return 0.0 from tableView:heightForHeaderInSection: - (CGFloat)tableView:(UITableView *)tableView heightForHeaderInSection:(NSInteger)section { return 0.0; } Seems like a real pain. I don't know why they changed this, as everyone relies on the prior behavior - but they must have their reasons.
Thank you! – flopes Aug 23 at 17:29 No problem. If you could mark my answer as "Accepted" when you get the change I'd be most appreciative!
– Steve Aug 23 at 17:30 2 What if there is a header? Does returning a height of zero override the height of the header? – Ryan Booker Sep 9 at 7:08 1 Ryan, in that case you should probably measure your header like you do with table cells and return that value.
– PEZ Oct 15 at 9:51 I think the header may be for aesthetic purposes. For example, I have a tabbed app, and one of the tabs didn't have section headers defined. When I switched to that tab, it always looked a bit off.So I will keep the empty header there for aesthetic purposes.
I don't think it will be confusing to users. – JPK Oct 15 at 20:23.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.