[snip] >>>> Are you sure that the first deposit gets reassigned in the case >>>> where >>>> it is a manual deposit? The matching code clearly attempts to avoid >>>> matching transactions that were manually set (in import-backend.c >>>> at >>>> gnc_import_TransInfo_refresh_destacc). >>> >>> Yes, I'm sure. I watched it happen in an import.
Oops. I think I've reproduced the event that I thought was a second switch. It wasn't after a cancelled import, but it was after I'd tried several different scenarios. When I edit the 3 transactions from bottom to top in the matcher window, the first transaction flipped from light green background (auto-assigned account) to yellow (new, unbalanced) after I changed the account of both similar transactions below it. I was just misremembering which time I had edited the account for the top transaction. Sorry for my screw-up. And thank you very much for taking the time to track down these bugs. Dave -- David Reiser dbrei...@earthlink.net _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
