Trouble With "Enter" vs. "Tab" (Again)

[Colin Law]

On 14 November 2011 18:24, David T. <sunfish62 at yahoo.com> wrote:
> John--
>
> I am sorry I missed the details about the Tab key moving to the next field, while the Enter key move to the next line. Frankly, to me that's not the point.
>
>
> Ultimately, the point is that the Enter key "finishes the transaction edit" but still keeps the transaction open onscreen. This misleads users, and will cause them to have the kinds of troubles I experienced. I *still* don't understand the reason WHY the Enter key finishes the transaction edit. If there is a functional use-case reason for finishing the transaction edit every time a user presses Enter, I'd really like to hear it. I trying to understand this.

That is the main purpose of the Enter key, that is the only way that I
ever finish a transaction edit, and that is the only reason I ever hit
Enter during a transaction edit.  Most of the time I do not use the
split mode of display as my transactions are mostly simple transfers
or money account to expense account transactions.  In that view Enter
is, I think, the only way of closing a transaction.  It certainly does
not mislead me or cause me to have the kinds of problems you have
experienced.

>
> In the absence of such an explanation, would it be such a horrible solution to remove the closing action of the Enter key behavior altogether, and instead have the closing action attached to the empty split situation (as it currently is when the user presses Tab on an empty line)? As an end user, I would be willing to go to Bugzilla and file an RFE bug request for this change, if it seems like it makes sense.

Definitely not, see above.

Colin L.