Thanks for your response, however, my “curiosity” is only one of App performance, not any “under the hood” revelations.
Of the Apps containing a UITableView I’ve created, I’ve never before experienced or observed such errant behavior.
I was hoping my post would be seen by a fellow developer that has encountered this issue before that could share the cause and their solution.
I should have included in my original post -
If you’re a developer that has encountered this or similar errant behavior implementing a TableView from a large data source with many sections and has resolved it, I’d love to hear from you as to how you resolved the issue. Thank you in advance.
Topic:
UI Frameworks
SubTopic:
UIKit
Tags: