importing happens even when transaction matcher told not to

[Derek Atkins]

Benoit Gregoire <bock at step.polymtl.ca> writes:

>> But in recent svn versions, this architectural problem has been made
>> worse. I've seen the transactions created by the generic import
>> matcher before, but the appropriate ones would be removed upon
>> Finalize. Now, the matcher seems to finalize based on whatever state
>> it guessed for the collection of transactions on initial import.
>> Changes made once the matcher shows the collection are ignored when
>> Finalize (and probably Cancel) is clicked.
>
> Well then, either something changed in the matcher behaviour or in the engine 
> revert code (so reverting a transaction no longuer really reverts). 

I know Chris WAS working on the engine revert code..  So it's possible
that some artifact of that code changed some behavior you were
depending on.

-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 at MIT.EDU                        PGP key available