Matt, the delay you guys implemented a week or so ago makes the first one or 2 page down screens display quite quickly, but after that, it still takes about 5 seconds to display the next page down. It used to take 7 seconds, so it's definately better, and thanks for that.
But (there's always a but), is there any way to either increase this delay you introduced, or perhaps, make scrolling have priority over checking against the database, no matter what. If I shift-click to the middle of the list, that view comes up pretty quick, but the next click is slow. If you could allow the display to draw without checking the database, we could scroll as fast as we want, and when we stop, the database checking can begin, until we try to scroll again, then checking will pause, until we stop scrolling.
Or maybe, the database checking can always be done in the background, i.e. it will check the entire list, whether or not it's visible, so when we go to scroll it's already been verified, again, it would need to stop checking if we scrolled before the check was finished, but once it's done, it's done.
Again, I have no programming experience, so maybe this is all hogwash (haven't heard/used that work in quite some time), but the fact that you were able to add this delay so quickly in the first place gives me hope that another little tweak will solve all my scrolling issues.
As a reminder, my entire database 7500 songs, 30,000 images are all stored on a LINUX server mapped in Windows.
Thanks