TAB KEY ONLY WORKS TO MOVE BETWEEN REGISTER FIELDS IF CAPS LOCK IS OFF. MOUSE SCROLL WHEEL NO LONGER WORKS TO SCROLL DOWN THROUGH THE ACCOUNTS LIST.
*** Bug 795360 has been marked as a duplicate of this bug. ***
The first problem is a duplicate of bug 795132.
As the first issue is fixed I have renamed the bug to focus on the scroll wheel issue.
Confused on the title, that was mentioned on the user list below that was withdrawn from gtk3. https://lists.gnucash.org/pipermail/gnucash-user/2018-March/075426.html Byron can you clarify what problem you are having scrolling, I read it that you can not use the mouse scroll wheel on the accounts page to scroll the accounts which works on my Windows 10 machine.
Bob, you're right I seem to be mixing things up. I thought the second part of this bug was about not being able to scroll through the tabs. But rereading it it looks like it mentions scrolling through the account list. And yes, this works indeed. To add to the confusion bug 795360 which was marked as a duplicate of this bug did report on not being able to scroll through the tabs. So that's a false duplicate. Byron, do you still have an issue scrolling down through the account list ?
Sorry, didn't explain very well, when in the register with several account tabs showing on the left of the screen, it used to be possible to use the scroll wheel on a mouse to scroll down through the account tabs to select a different one, this now is not possible even after the update to ver 3.1.
Just downloaded ver 3.2, issue with scroll wheel still not been addressed. Used to be possible in the account register page to scroll up or down the account tabs to open a different account, this is no longer possible.
I think this is what Byron is talking about: https://gitlab.gnome.org/GNOME/gtk/issues/234 There's mention of a "workaround" being removed from Gnome Terminal, but also lots of opposition from the core Gtk developers Emmanuel Bassi and Mathias Classen. Bob, if you think we can and should take the code removed from Gnome Terminal, go ahead; otherwise I think we should close this as NOTGNUCASH.
As John points out this is really a bug (or feature removal) in Gtk+, not something in the gnucash code. I don't think it's up to gnucash to fix this. If someone feels inclined, go ahead and fix the patch on the gkt bug above and the feature will return in gnucash as well. Thanks you for your report.
