Remembering the last transaction keyed...

[Jroonk]

I really like that they added remembering the last transaction for keying in a new transaction, but they are doing it wrong. It remembers the last dated transaction in the database, rather than the last keyed transaction. My problem is, I always put my repeating transactions in several days early. So my default transaction when I key in a new transaction is always my future repeating transaction. I would rather it remember the last thing I keyed.

When I have a bunch of receipts from one place, a few days previous, I have to manually key them all because it looks at my last dated transaction, not my last keyed transaction. If other people like it the way it is, then make it an option please. But I can't see how the last dated transaction is useful as a default for keying new transactions.

[Nikolay]

I have created this function.
When user is adding new transaction, the payee and category values used like previously entered for this account.
I've tried other algorithms, such as using previously imposed posting, but not today. It's better.
For example, every day I have enter for my Cash account the next transactions.
Transport = 60
Dining Out = 200

if Dining Out has entered the next one will be Transport

In any case, this function is rarely used , as your shoul copy the entry,rather than creating new ones.