if the cursor is on a tx in the register and I press Enter nothing happens. I have tried changing the Edit / Pref / Register / Action settings and it doesn't make any difference. I can still navigate between transactions in the register by using the mouse. If I use the toolbar (I usually have it hidden) the Enter button doesn't do anything either but the Blank button does move to the blank tx line as expected. New in 3.7 Win 8.1
Sounds like bug 797399.
I did look at that first but what I'm reporting happens when in basic view (i.e. without splits showing) and the other report says that basic view works. I've no problem with them being merged if they are slightly different artefacts of the same problem.
Looks like it was my change in gnc-split-reg.c, it works if there is a change to make but on no change it does not move, need to have a think.
I am using Ctrl-PgDn instead of Enter which works fine for me. Bob, do you think this is a dup of Bug 797399 ? I'm thinking it probably is now.
(In reply to Wm from comment #4) > I am using Ctrl-PgDn instead of Enter which works fine for me. > > Bob, do you think this is a dup of Bug 797399 ? I'm thinking it probably is > now. It may have, need to reread that bug, have an idea to fix this but will need to do some testing.
I have pushed my change to maint and will be in the next release, if you would like to try it, it should be in the next nightly but I think there are build problems at the moment. Please report back if fixed.
I did a build of maint this morning on Mint 19.1 using Cmake and Ninja. Build was essentially clean and installed with no problems. Fyi, Build Id is 'git 3.7-76-gacf527096+(2019-09-27)' Problem seems to be fixed. I can use the Enter key now to move through transactions in the register and lines in a split just as before. The items do not need to have been changed. As far as I can tell, all the basic functionality appears to be ok in this build as well, though I haven't done comprehensive testing.
*** Bug 797231 has been marked as a duplicate of this bug. ***
*** Bug 797529 has been marked as a duplicate of this bug. ***
I upgraded from v3.7 to 3.7-305 just now. While the Enter key does work to move to the next line in the register, it is also moving to a different column. In all previous versions, if the cursor was in the Description column when I pressed Enter, the cursor would move down to the next row of the same column the same as if I pressed the down arrow key. In 3.7-305 when I press Enter the cursor moves to the Date column.
I'm not sure there was ever a design saying which column Enter or PgDn should land in. I tend to use Enter or PgDn for BlankTx and UpArrow DnArrow for moving between lines. UpArrow and DnArrow seem to preserve the column.
