Thanks for that suggestion. I'm only reloading visible cells, so I would expect them to already be instantiated and readily available in memory. However, if cellForRow... is called, I guess there is an attempt to dequeue. I'd have to take a look at how much time is spent in that method.
At any rate, it's clear that all of this can be done with adequate performance. The problem only occurs when the table is scrolled within a 50-pixel range of position, and that position varies (so far unpredictably) with row height. If the table is scrolled more or less than that, it works fine. The number of animating rows makes no difference (and there are only a few anyway). And performance isn't the only issue; the rendering is defective, with elements (like simple text labels) being rendered slightly out of position and cell images flying up from the bottom of the screen and settling into place. _______________________________________________ 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
