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. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
