On Monday, June 10th, 2024 at 00:30, Fred Bone <[email protected]> wrote: > > On 08 June 2024 at 15:03, Dale Alspach said: > > > If I directly enter a transaction in a register, the default date for that > > register gets reset to the date of the newly entered transaction. If I use > > "duplicate" to create a new transaction, the default date is not reset. > > Why? > > > What do you mean by "default"? > > I wouldn't expect the blank txn to change just because I duplicate > something else. And when I modify the blank txn and commit it, I expect > the new blank txn to inherit whatever date I'd committed with. > > FWIW, I'm on 2.6.21.
I'm still on a 2.6.21a, plus a swateh of patches I've applied over time to try and get it using a later webkitgtk so that it compliles natively against newer OS distro versions, and I do see the behaviour that Dale describes. Always assumed that, because the duplication process offers one the chance to set the new TXN's date in its own dialog, it doesn't interact with the register's "current date", which is the last date entered manually, or "today", if you haven't yet entered anything? I actually like the fact that the last date one entered, manually, "percolates" down into the next empty TXN, as it helps with entering multiple TXNs from the past. And, of course, it's easy enough - type "t" in the date column to get (t)oday's date - to get back to "today", if that's the date on which you want to make your next entry. Just my thr'pen'th. Kevin _______________________________________________ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: 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.
