[it's been like that for a long time -- before v100]
Using the down arrow to go from item to item after reaching the bottom of the grid (not the actual total list of displayed item, but really the bottom of what's *visible*) isn't smooth.
Once the focus reaches the bottom, it doesn't "scroll" smothly, one item at a time : it becomes somwwhat sluggish, jumpy/unsteady, and the focus is hard to follow.
It can suddenly jump 2 or 3 items above the bottom of the grid. This is especially true while word wrap is ON, but it also happens otherwise, if some other column has wordwrap on.
Really difficult to work on a long list. [If it's somehow hard to reproduce, I can make a screencast.]
Important note : the problem doesn't exist going upwards (up arrow).
It's possible that this occured after trying to fix some other scrolling bug, but I'm not sure if it's not worth it if it makes navigating a long list that difficult on the eye (and the brain).
Comments
I tried in a sample DB, and the jumpiness is obvious. Maybe you tried with items containing only one short line of text each?
In any case, here’s a screencast.
1- If you completely scroll down the grid, and focus on the "first" item at the top of the grid's visible area (so: many items invisible at the top), and then move upwards with the up arrow, one item at a time : the cell position is steady, sticking to the top of the window/grid. There are no items suddenly appearing between the border and the focused item.
2- In comparison, going down with the arrow, one item at a time is inconsistent. Items appear between the border of the window/grid, and the focused item. It's jumpy, hard to read when you're going through a list and performing operations on each item at a relatively quick pace. (Understandably, focus "jumping" is a problem for most people -- a quick look at the forum will confirm that statement.)
*To IQ's "defense", Excel always suffered from the exact same problem* in word wrap mode -- as it is a problem. Wonder if has to do with approximating the row's height with the numbers of chars inserted, instead of first retrieving the actual height before moving down, and at least leaving one part of the cell stable : the bottom or the top... Not sure, but everything moves, the top, the bottom. Cell pop corn!
Don't know how to circumvent the problem in Excel, but there’s an ad hoc workaround :set a static row height on the fly whenever you need it (Home>Format>Row Height, or Alt,O,R,E). It doesn't always let you see the whole content, obviously, but more than just a line, if you want (I like 5-8, depending on the width of the column, which is usually enough to get enough content from a multiline cell).
columnrow, on the fly, could also be useful. Eventually)