Bug: Transaction is Committed instead of Rollback'ed

[Derek Atkins]

Part of the problem, I think, is that nothing ever calls the backend
'trans_rollback_edit()' method.  Simiarly, the xaccTransRollback()
function winds up making changes to a transaction by hand which, if
force_it gets set, winds up committing the transaction which really
never got changed.  This seems like a bug to me; I'm not sure what the
right way to fix this is.

-derek

Derek Atkins <warlord@MIT.EDU> writes:

>   * Open an account
>   * Start to edit a transaction
>   * when the popup asks "The current transaction has been changed.
>     Would you like to record it?" hit "No"
> 
> At this point the transaction is still committed (although without the
> changes).  The account is _not_ Rolledback, which is what I would
> expect to happen.
> 
> -derek
> -- 
>        Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>        Member, MIT Student Information Processing Board  (SIPB)
>        URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
>        warlord@MIT.EDU                        PGP key available
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel@lists.gnumatic.com
> http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord@MIT.EDU                        PGP key available