Disable "Wraparound" of next/previous sheet shortcut in Calc

I’m a long-time Calc fan and user, and in a relatively recent update I’ve noticed that the CTRL-PGUP/CTRL-PGDN shortcuts for switching sheets behave differently.

Previously (as recently as 7.6.4.1), once on the very first or last sheet of a workbook, using the shortcut CTRL-PGUP or CTRL-PGDN would stop.
This behaviour was:

  1. Consistent the GUI buttons for “Scroll to next/previous sheet”, which do nothing once you are at the “end” of the strip.
  2. A convenient and long standing way to return to the start/end by holding the keyboard shortcut - essentially a shortcut to “Scroll to last/first sheet”.

In a recent update, this keyboard now “wraps around”, so that the selected sheet infinitely returns from the start to the other end.
This is inconsistent with the GUI, and breaks prior behaviour for now reason.
Is there any setting to revert this, or is it simply a bug that needs fixing?

3 Likes

https://wiki.documentfoundation.org/ReleaseNotes/24.2

2 Likes

This implies that you know reasons… Indeed it was for a reason (tdf#156311 starts with a user explicitly asking for this newly implemented behavior). However, since you likely have a reason to keep the old behavior, you might want to create a new bug, where you present your reasons, and request a configuration.

2 Likes

Thanks Mikeand also to PKG for linking to the release notes.
I did do a Web search prior to posting here, but I failed to find that, so thanks!

I’ll put a feature request in for a config option.

1 Like

Did you add the feature request? If yes, please mention the URL. It may be useful for others.

Seems to be tdf#160580

4 Likes

Yes please! Unexpected changes forced on long-time users with no opt-out are what the likes of Google and Microsoft do! Please could we at least have a config setting to stop this new wraparound? That would be much appreciated. My spreadsheet tabs are always very structured, and I rely on it stopping at the first or last tab, and it makes no sense to endlessly wrap around.

@DenM: since you are interested, and you are a developer: you are welcome to contribute (I provided a code pointer there in the bug).

But note that “what the likes of Google and Microsoft do” is not a bad thing by itself (no need to try to demonize based on names). In general, each simple boolean “simply” doubles the space of program states, making it even less possible to test “fully”.

Thanks for your reply. I am very much a former coder. I’m not sure 6502 assembler is a lot of use to this project! I wasn’t trying to demonize based on names. I was simply saying that their typical behaviour is the problem, which is that of insisting that end users must accept the arbitrary changes in their new software, regardless of whether those users are old, young, can see very well, have had 30 years of a different workflow, etc.etc.etc. The change here is neither right nor wrong, but it does seem arbitrary. Another recent arbitrary change was to separate the “Recent File” list based on which application (Writer, Calc, etc) was being used. Many users also didn’t like that arbitrary change, and there is a config boolean to change that back to previous behaviour, which seemed an excellent solution all round to me. I was hoping for the same here.

1 Like