Question

I just inherited code which hides/shows rows a UITableView by using the delegate heightForRowAtIndexPath method and returning height 0 for “hidden rows”.

The code works, but it has me concerned there might be fraught with unforeseen complications. Can someone either ease my concerns or give me good reasons why this could cause problems (I couldn’t find any issues with initial testing).

The table is fairly small <10 rows total and would require custom row heights even without this hidden row solution.

Answer 1

It would be cleaner to add and remove the rows between two beginUpdates and endUpdates calls, but I don’t see why this 0-height method should not work.

If there are no UI-artifacts, that is (e.g. the Delete button showing up overflowing to the next cell).