https://bugs.kde.org/show_bug.cgi?id=289351
--- Comment #9 from allan ---
I've come back to this after a couple of diversions.
Cristian's fix was inadvertently removed after 4.6.3
This fix allowed a multi-transaction memo edit to have a blank field, albeit
with a space character to trigger a co
https://bugs.kde.org/show_bug.cgi?id=323788
Cristian Oneț changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=323788
--- Comment #3 from George Baltz ---
git bisect between HEAD and 4.6.4 gives this result:
gwb@cloyd:~/kde/src/kmymoney> git bisect good
7683caffba5f748301e140d276b25f985a9093dd is the first bad commit
commit 7683caffba5f748301e140d276b25f985a9093dd
Aut
On Mon, 21 Oct 2013 14:47:55 +0100
aga wrote:
> I'm importing transactions including transfers between two accounts at
> the same bank, and some which I expected to match were not being
> imported. Eventually I realised that they were being treated as
> duplicates.
>
> It appears that this happ
I'm importing transactions including transfers between two accounts at
the same bank, and some which I expected to match were not being
imported. Eventually I realised that they were being treated as
duplicates.
It appears that this happened even though the memo fields were
different. I use the
Julien,
doesn't the 'Networth graph' with a few configurations on your side give you
the information you are looking for? This one includes an option called
'Include Transfers'.
Hope that helps.
Regards
Thomas
On Sunday 20 October 2013 11:15:44 Alvaro Soliverez wrote:
> Hello Julien,
> The
I am in contact with Thomas to develop online banking support
(outgoing transfers, affects german users only). The transfer
forms could be done with qml in a beautiful way.
Am Montag, 27. Mai 2013, 07:36:17 schrieb Alvaro Soliverez:
> not at the moment. What were your intended changes?
>
> Rega
Hi Trevor
I suspect you haven't subscribed to the mailing list and therefore
haven't seen my reply -
On Sat, 19 Oct 2013 14:40:40 -0700
Trevor Currie wrote:
>> Hi,
>>
> I think this software is pretty good!
> Snap!
>
>> I'd like to recommend a few features:
>> * schedule bi-weekly pa
