: 4 : 4 : 0 |
When a view gets dirtied during a scroll-up, the navigation sequence (pgUp, pgDn) flies to the top or bottom of the view collection. I'd like it if something could be done to address that issue.
Something like that's also happening, apparently much more often, to NotesViewCategory objects. The view collection gets dirtied, and suddenly NotesViewCategory navigation goes scanning and scrolling to the end of the collection.
Turning a view to "AutoUpdate == false" actually seems to aggravate the problem (up to ND7 it alleviated the problem somewhat), especially if the code that's scanning the documents is actually updating documents so as to impact their view positioning. But with 8, it seems the problem is bigger for NotesViewCategory objects.
NotesViewCategory objects take a long time to generate, so it's generally a losing battle to simply re-create them at present. There needs to be a way to either hold the view in place while processing it, or detecting a change to the view and efficiently re-creating the category object or correcting it.
|