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

[Geert Janssens]

On maandag 14 november 2011, David T. 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.

I don't know the details of all of this, but from what I've read here and 
there in the code, there are a few things related to this:
1. value fields in the register can be used for calculations (try entering 6+8 
for example). Hitting enter  on such field will execute the calculation and 
replaces your "formula" with the calcuated value. And then it stays in that 
field so you can quickly correct if you think the value is not right.
2. You could also hit the return key instead which will move you to the next 
line at once after running the calculation
3. The tab key will run the calculation and move you to the next field.

I don't know why the transaction itself if fully evaluated though. I don't 
think this is necessary for the calculation. I wouldn't mind if the behaviour 
were more consistent in that a transaction is only completed when you are 
really about to leave it. I don't see a use case either for the confusing 
state we have now.

Geert