Profound UITableView rendering-performance problem, but only at certain positions? No, not resolved.

  • Actually, I spoke too soon.  This problem continues to occur, but the
    critical position of the partial row at the top varies with the table's row
    height.  And it's not even always the bottom portion; sometimes if the last
    row in the previous section is cut off in a middle region, rendering will
    degrade to unusable.  Move the thing up or down a bit, and rendering
    performance returns to normal.

    So there really is some bad math going on in UITableView, but I have no
    idea what the numerical relationship is between row height and the zone
    that triggers the rendering problem.  I had to print out the tableview's
    scroll offset and then hard-code a workaround into my app.  If the top row
    sits in the danger zone, I scroll it up off the screen.
previous month july 2012 next month
MTWTFSS
            1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30 31          
Go to today