Display items ahead when scrolling up/down the list

[PeterH]

Tested KeyScrollMargins=2 > fine!!!
(No crash for me )

Didn't expect 2 empty lines appearing when going to bottom. While at top the 1st line is kept - yes: at the very top
But: not really a problem.

To ask: wasn't there a chance to 'dynamically' set some tweaks? Don't find info. Would be fine if it would be possible here

[admin]

Fixed.

1:0

[TheQwerty]

To ask: wasn't there a chance to 'dynamically' set some tweaks? Don't find info. Would be fine if it would be possible here

Some can be modified via script with the undocumented tweak function, but this new tweak is one of those that it does not support (yet).

[PeterH]

Ah - undocumented! Really forgot "this strange kind of behavior"! So thanks

To say: I wish it here

[TheQwerty]

CRASH!

From fresh v17.70.0103:

1. Set Configuration | Styles | Grid style to Alternate Groups (Smart Names).
2. Enable #408 Tools | Customize List | Show Grid.
3. Set KeyScrollMargins=5 - 5 is not important, but the actual value does make a difference in ways not clear to me.
4. Navigate down all the way to the end of the list.

It almost looks like the grid styling is not calculated until the items are listed and with this tweak if the style is not calculated yet there can be a crash when entering the group. Maybe? I'm not sure.

Fixed in v17.70.0104!

[RalphM]

I tested this and even before adjusting KeyScrollMargins when scrolling down in the list by key down the focused line was always the 2nd but last, going up it always focused the topmost line.
After changing the value to KeyScrollMargins=2, I now always have 3 lines below the focused one on the way down and 2 lines above on the way up.
Something wrong with the calculation here or something else influencing this on my system?

[autocart]

I tested this and even before adjusting KeyScrollMargins when scrolling down in the list by key down the focused line was always the 2nd but last, going up it always focused the topmost line.
After changing the value to KeyScrollMargins=2, I now always have 3 lines below the focused one on the way down and 2 lines above on the way up.
Something wrong with the calculation here or something else influencing this on my system?

This happens to me if the height of the list view control is *almost* as high as a full number of rows (minus 1 or 2 pixels). In this case it may *look* like the last row is fully displayed but for XY it is not, which optically adds that row at the bottom but not for matters of internal calculation.
If I increase the height of the list view control by a few pixels so that it barely shows the beginning of the next row, then it also *looks* as expected.
I hope I could explain my thoughts understandingly.

[RalphM]

So you seem to confirm that my first suggestion is true - something wrong with the calculation!
Not a biggie anyway, just thought I put my findings out there...

[sinilill]

Nice feature, thanks. I also have a another tweak enabled, it had something to do when navigating the list upwards. When going the list up (with up key)and the selection is right on top of the list, then it would automatically schroll <n> lines. Now I have both tweaks enabled and the upwards navigation is "jumpy". Unfortunately I don't remember the tweak anymore and can't disable it. Does somebody know the tweak?

[highend]

ListRowForAutoScroll= ?

[sinilill]

ListRowForAutoScroll= ?

yes, thank you

[admin]

So you seem to confirm that my first suggestion is true - something wrong with the calculation!
Not a biggie anyway, just thought I put my findings out there...

No, nothing is wrong. It's as autocart said: the last focused line must be fully visible, else it's scrolled one up to make it fully visible. Windows standard ever since.

[admin]

ListRowForAutoScroll= ?

Indeed, the combination of both tweaks makes it jumpy. Probably the days are counted for ListRowForAutoScroll . I don't see much use in it anymore.

[kinook]

It would be great if the new setting applied to PageUp/Down as well. Thanks.

[highend]

It would be great if the new setting applied to PageUp/Down as well

Good point! + 1