<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Jack<br>
<br>
I suspect you are correct. I was hoping someone would recall the
reasoning so we could work on a fix with all the necessary info.<br>
<br>
If the reason has been lost in the mists of time. Then I'll clean
up my code changes (which were very rough just to do the testing)
and put it in for review.<br>
<div class="moz-signature">
<p>Chris<br>
<a href="http://www.rebel.com.au">Rebel Software</a>
</p>
</div>
On 26/04/2014 9:55 AM, Jack wrote:<br>
</div>
<blockquote cite="mid:1398471928.28915.0@ffortso4" type="cite">I
vaguely recall that this has come up before, with about the same
(lack of) remembered reason for the restriction. However, given
that you found multiple explicit checks, whoever developed that
bit of code must have had a reason, although perhaps we are lucky
enough that it simply doesn't apply any more. I suggest filing an
enhancement request at bugs.kde.org (if there isn't already one -
I haven't checked) just to put it officially on record. If you
have already looked into the code, then a reviewboard request
might not be out of order.
<br>
<br>
To be long winded, I suspect what may have changed since that code
was written was the general use case. At that point, the most
common scenario (yes, I'm just guessing, but ....) was KMM mostly
used manually, with someone just starting to download and import
statements from either a bank or credit card. Now, with
ofx-direct connect (and I suppose aqbanking and other methods I am
not familiar with) we have accounts where the primary input is
importing, and transactions between accounts each of which has its
own primary import are now much more common.
<br>
<br>
Jack
<br>
<br>
On 2014.04.25 20:11, Chris wrote:
<br>
<blockquote type="cite">No Takers?
<br>
<br>
I have commented out the checks that prevent the matching of
imported transactions. KMM then correctly manually matched the
transactions. I haven't had the opportunity to test matching
during import.
<br>
<br>
So the remaining questions is why was matching disabled on two
imported or two manually entered transactions. There was checks
to prevent it in at least 3 different locations.
<br>
<br>
Is there a subtle bug that creeps in if these checks are
removed?
<br>
<br>
If there is no (remembered) reason to prevent the matching of
imported files then I suggest this "feature" be removed. Though
this feature is documented there is no documentation I could
find that gives a hint as to why.
<br>
<br>
Chris
<br>
<br>
On 25/04/2014 10:13 AM, Chris wrote:
<br>
<blockquote type="cite">Hey all
<br>
<br>
I am having an issue with imported transactions not being
automatically matched and manual matching is disabled.
<br>
<br>
both transactions are the result of seperate imports one from
my credit card statement the other from a bank statement
<br>
<br>
both transactions are for a payment from my bank account to
the credit card
<br>
Both are on the same date with the same amount the only
differences are the memo and payee fields
<br>
<br>
They should have automatically matched. but didn't and I
assume because they are both imported I cannot manually match
them.
<br>
<br>
Questions
<br>
<br>
1/ How can I correct this?
<br>
2/ What is the thinking behind disabling the matching when
both are imported or manually entered?
<br>
<br>
documentation is here..
<br>
<a class="moz-txt-link-freetext" href="http://docs.kde.org/stable/nl/extragear-office/kmymoney/details.ledgers.match.html">http://docs.kde.org/stable/nl/extragear-office/kmymoney/details.ledgers.match.html</a>
<br>
<br>
<br>
<br>
<br>
</blockquote>
<br>
_______________________________________________
<br>
KMyMoney-devel mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:KMyMoney-devel@kde.org">KMyMoney-devel@kde.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/kmymoney-devel">https://mail.kde.org/mailman/listinfo/kmymoney-devel</a>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
</body>
</html>