Glad you found a solution that works for you, although I’m scratching my head about your comment regarding “tabbing through” autofill. Once autofill supplies you a transaction, the entire transaction is duplicated (including notes and comments), and pressing enter commits it, which is a pretty quick process, all told. There is no need to tab through all fields.
Regardless, glad you have it sorted. David > On Apr 25, 2016, at 5:45 AM, will Snow <[email protected]> wrote: > > Thanks David, > > I found autofill takes longer, it's quicker to duplicate the record and > just enter a date rather than tabbing though and autofilling. However, > it looks as though the scheduled transactions feature solves the issue > I was having. > > Thanks again, > Will > > Sent: Saturday, April 23, 2016 at 2:13 PM > From: David <[email protected]> > To: "will Snow" <[email protected]>, [email protected] > Subject: Re: How the date populates when transactions are duplicated > > Will, > > Not that I'm a programmer or anything, but I can't see why you'd do > this. It seems to me that a user could set the date to their starting > point and use autofill to create their transactions. Having yet another > preference setting will only add to general user confusion, I think. > > David > __________________________________________________________________ > > From: will Snow <[email protected]> > Sent: Sat Apr 23 06:35:46 EST 2016 > To: [email protected] > Subject: How the date populates when transactions are duplicated > > Hi All, > > I noticed that when transactions are duplicated the date field uses the > latest d > ate rather than the date of the original transaction. I tend to do my > accounts a > ll at once towards the end of the year so this seems to slow me down quite a > lot > as I have to enter an entire date all the time rather than just bumping up the > day in the date field. So I was thinking about adding an option somewhere > where > the user can specify how the date field populates on duplication (or perhaps > thi > s already exists?). > > It looks as though the relevant code is inside > src/gnome-utils/dialog-dup-trans. > c > and the flow goes as: gnc_dup_trans_dialog -> gnc_dup_trans_dialog_internal > -> g > nc_dup_trans_dialog_create > > Moreover, it looks as though date and date_p are key variables but I'm not > sure > on where to pull the date stored in the transaction in the parent window. Or > if > I should be doing it in some other way? > > Any advice is greatly appreciated. > > Thanks, > Will > __________________________________________________________________ > > gnucash-devel mailing list > [email protected] > [1]https://lists.gnucash.org/mailman/listinfo/gnucash-devel > > References > > 1. https://lists.gnucash.org/mailman/listinfo/gnucash-devel > _______________________________________________ > gnucash-devel mailing list > [email protected] > https://lists.gnucash.org/mailman/listinfo/gnucash-devel _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
