Feel free to log such things as feature requests for AppKit. What you
are wanting is basically a lazy-push model (all the data is pushed
into the view lazily) as opposed to the current lazy pull model (all
the data is pulled when the view needs it).
I don't want a push model: I don't want the table view to cache all
the data it ever displays, just the data for the currently selected
visible rows (because it is likely to need it again when the rows are
unselected). But thinking about it a bit more, this would be rather
inefficient when scrolling down a large table in which all the rows
are selected, so I should probably be more careful what I wish for :)
For that same reason, wouldn't it also be cool to have an inverse
method to: