GNOME Bugzilla – Bug 450717
Ctrl+PgUp and Ctrl+PgDn keyboard shortcuts not working in register window
Last modified: 2018-06-29 21:40:33 UTC
Please describe the problem: The Ctrl+PgUp and Ctrl+PgDn keyboard shortcuts which supposedly mean 'previous tab' and 'next tab' does not work in a register window, if the contents of the register is more than a single page can fit (in other words, the keys don't work if the register's scroll bar(s) is enabled). Steps to reproduce: 1. From "Accounts" main window, open any account's register whose contents are longer than what a single page can fit. It should be opened as a new tab. 2. Try pressing Ctrl+PgUp or Ctrl+PgDn from that register window. Actual results: In the register window, the Ctrl+PgUp and Ctrl+PgDn keys would give the same action as PgUp and PgDn (i.e. move up and down one page). This would not happen if the register's contents are short enough to fit just one page. Expected results: Moving to a different tab. Does this happen every time? Yes. Other information: OS: UBUNTU Linux 7.04 on a Pentium M machine.
Does Ctrl+Alt+PgUp and PgDown work? I know this should be documented more clearly, but AFAIK that keyboard combination should work every time.
There is a tip-of-the-day for it (not yet in gnucash 2.0.2, i think). Feel free to add other documentation as well.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
OK. I tested that Ctrl+Alt+Pg** did work with 2.0.2 . But I still think the Ctrl+Pg** keys should always behave like "next/previous tab", since that's what user intuitively expects.
Confirmed. That is what users expect, and how we should behave.
This also happens in the Accounts tab. In fact Ctrl+Page* is not exactly the same as Page* but it grabs the shortcut anyway. I notice this happens in register windows even if the content is smaller than the screen can fit. This does not happen every time. If you select an entry in a register window for example, further shortcuts are grabbed, but if you click on the tab (name), the shortcut will work for all tabs.
The bug still exists in version 2.6.4 on Debian. The latest stable update (2.6.5) has not reached the repositories, but I do not see any mention of the issue in the release announcement. Ctrl+Alt+PgUp and Ctrl+Alt+PgDn work fine. Clicking on the tab name, allows me to cycle through the tabs with Ctrl+PgUp. However, attempting to cycle with Ctrl+PgDn will fail when I reach a register tab. Notes: - Bug 647744 is a duplicate, but I don't seem to have the privileges to mark it so. - There still exists a Tip of the Day which reads "To switch between multiple tabs in the main window, press Control+Page Up/Down." - Sadly, the Gnome HIG doesn't give much detail on switching between windows and tabs. (https://developer.gnome.org/hig/stable/keyboard-input.html.en) Instead, they have only this guideline: "PageUp, Ctrl+PageUp, PageDown and Ctrl+PageDown Scroll the selected view by one page up/left/down/right" Best case scenario: the bug is fixed. Second best: Users are temporarily required to use the current keyboard shortcuts and all faulty documentation is removed until the bug is corrected. Third Best: Users are required to use the current keyboard shortcuts and all documentation is corrected to reflect that fact.
The GNOME 3 HIG says this: > When using dynamic tabs, ensure that the standard keyboard shortcuts are supported. > Ctrl+Page Up Switch to the next tab > Ctrl+Page Down Switch to the previous tab https://developer.gnome.org/hig/stable/tabs.html.en Can we have that at last, please? The objection that the tree view control binds Ctrl+PgUp and Ctrl+PgDn is groundless. What it actually uses them for is to scroll a page up or down without changing the selection. It would make a bit of sense if the account tree allowed multiple selection. But it does not, so there is no reason to preserve these shortcuts.
Only assigning to default.
*** Bug 647744 has been marked as a duplicate of this bug. ***
GnuCash bug tracking has moved to a new Bugzilla host. The new URL for this bug is https://bugs.gnucash.org/show_bug.cgi?id=450717. Please continue processing the bug there and please update any external references or bookmarks.