gnucash bugs

Dave Peticolas dave@krondo.com
10 Jun 2001 14:47:36 -0700


On 06 Jun 2001 23:57:17 -0700, Gregg Morris wrote:
>  I think I have a bug in gnucash.  When I save a new transaction it
>  always gets saved on the line before the last transaction.  For
>  example, a transaction dated 5/25 is the last one in the register.  A
>  new transaction dated 6/6 is saved.  Instead of saving on the last
>  line, after the 5/25 transaction, the new one gets saved on the line before
>  the 5/25 transaction.  Then I have to delete the 5/25 transaction and
>  re-enter it in order for it to save to the correct place.  I am
>  sorting by date.

I'm not sure what is causing this. If you save and restart is it still
out of order?


> The other thing is that checks that are marked 'c' in the register are
> automagically changed to 'y' when I go to reconcile.  This is
> undesirable behaviour for me because I check with my bank several
> times per month to see what checks have cleared.  In the last release,
> the cleared checks stayed 'c' in the reconcile window so I could check
> them against the statement.  Now, I have the harder task of figuring
> out which checks have *not* been posted to the statement and
> un-checking them.

Ah, ok. This was supposed to make reconcile faster, but apparently
it doesn't help everyone :) There won't be any more 1.4.x versions,
but I will add this option to a later version of 1.6.

thanks,
dave