On Sun, Jan 07, 2007 at 03:09:34PM -0800, Thomas Bushnell BSG wrote: > On Sun, 2007-01-07 at 15:16 -0600, Jamuraa wrote: > > I was putting my receipts in for the last half month or so recently > > and noticed that I had to be careful to notice the year that the > > receipts were in. When putting in 12/23 or similar, I didn't get > > December 23, 2006, but December 23, 2007. I thought this should be > > different, so I dove into the gnucash code and changed qof_scan_date > > slightly to choose the last year for December if the current month is > > January. The patch is attached. > > This behavior has also always annoyed me.
me too! but it only crops up once a year. How long after 1/1 are people still entering 12/xx items? Granted, I routinely enter 50+ items from the previous month, so its been particularly annoying. But I think, in terms of gnucash doing exactly what is expected, entering 12/31 and getting 12/31/07 makes sense. It is totally predictable in all cases that the year *will* be the curent year. Anything else would introduce uncertainty in its behavior and that's probably bad IMO. .02 A
signature.asc
Description: Digital signature
_______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
