I put in some special case code for now so that if a clean transaction is committed, each split is then committed so that dirty splits in a clean transaction will be written to the db. However, if a split is deleted from a transaction, the deletion is never committed so the db now has an out-of-balance tx.
Two solutions: 1) better split handling in the register so that dirty splits are handled properly even if the tx has not been modified 2) If a split is dirty, mark the tx dirty too Comments? Phil _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
