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

[trythis]

Sorry for answering in the middle of the thread, but I had an idea while
using GC the other day very much related to this issue.. 
 I tend to go through 6 months of several accounts at a time, instead of
weekly or monthly maintenance. This results in a lot of corrections
requiring edits in many consecutive journal entries. 

 I would love to see [Enter] jump down to the next transaction (either
mirroring the last field location or always in the Date field) causing a
"settle splits" action. Let [Tab] move around in the split environment and
*not ever* leave the current transaction. Pressing the [Tab] key at the last
split, last value would result in returning to the date field of the current
transaction.  This would differentiate the two, [Enter] and [Tab] and still
keep the [up], [down], [left], and [right] arrows to provide flexible
keyboard navigation. They should have the ability to navigate out of the
current transaction causing a "settle splits" action just like clicking
outside a transaction does. 

This way, you know what [Enter] does, and [Tab] would never surprise you.

I like the idea of Enter also being able to create a new entry as currently
available in preferences.

Sadly, I am unable to contribute code, just user experience.


John Ralls-2 wrote
> 
> On Nov 14, 2011, at 10:24 AM, 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.
> 
> ....edit.....
> As written, gnucash makes your change and moves the focus to the next
> account. If Enter behaved like Tab, you'd have to
> advance across the whole transaction (5 enters) or go back to the mouse to
> click in  another transaction to get it to close. 
> In Split view, you'd have to go through every field of every remaining
> split, or arrow down, or click in another transaction.
> 
>> 
> ...edit....
> 
> Regards,
> John Ralls
> 
> 
> _______________________________________________
> gnucash-user mailing list
> gnucash-user@
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
> 


--
View this message in context: http://gnucash.1415818.n4.nabble.com/Trouble-With-Enter-vs-Tab-Again-tp4036073p4102142.html
Sent from the GnuCash - User mailing list archive at Nabble.com.