https://bugs.kde.org/show_bug.cgi?id=327497
canonknipser changed:
What|Removed |Added
CC||siekmannfr...@gmail.com
--- Comment #4 from cano
Hello William,
>From the code I can see where the problem might be. It's using a fixed
starting date instead of the day of the first purchase.
I have to check, but it does a similar thing with the finish date.
Regards,
Alvaro
On Tue, Nov 26, 2013 at 11:12 AM, William H. Haller wrote:
> The value
https://bugs.kde.org/show_bug.cgi?id=328127
allan changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=285761
Alvaro Soliverez changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=328127
Bug ID: 328127
Summary: mymoneystatementreader.cpp matching problem
Classification: Unclassified
Product: kmymoney4
Version: git master
Platform: Mint (Ubuntu based)
OS: Linux
Hi Chris
I think I've got to the root of the different results between OFX and
CSV import, if you are interested.
There were a couple of problems. The first was actually in the code in
MyMoneyStatementReader::processSecurityEntry() (starting on your on line
498). Using the CSV importer, th
https://bugs.kde.org/show_bug.cgi?id=285761
Andreas Stempfhuber changed:
What|Removed |Added
CC||kdebu...@afulinux.de
--- Comment #10 from
Yes, the patch fixes the OFX imports that were causing a messagebox saying the
transactions would be ignored. Now they find the existing security by ticker
and use it for the imported transactions.
--
Chris
On Tuesday, November 26, 2013 02:02:39 PM Allan wrote:
> I'm still investigating, but
On 26/11/13 17:28, Chris Tucker wrote:
Yes, the patch fixes the OFX imports that were causing a messagebox saying the
transactions would be ignored. Now they find the existing security by ticker
and use it for the imported transactions.
--
Chris
OK, Chris, thanks. I was pretty sure you ha
The values I reported were with the Date range set to All Dates and were
for closed positions. If it is trying to use anything other than the
prices at purchase and sell for a closed position, then it is
fundamentally broken.
My comment "I can't say what it is using for dates" simply reflected
On 26/11/13 13:59, Zdeněk Elis wrote:
Hi,
my feature request is to add category and subcategory into csv import
Thank you
Zdenek
Please see the thread started by lp.allar...@gmail.com on 12 Nov.
Allan
___
KMyMoney-devel mailing list
KMyMoney-devel@kd
I'm still investigating, but have now added your patch, and it makes no
difference here. statementTransactionUnderImport.m_strSymbol.toLower()
is empty, but a match is still found on the security name. Strangely,
at the moment, on iterating through the list, it doesn't match with the
existing
Hi,
my feature request is to add category and subcategory into csv import
Thank you
Zdenek
___
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel
The investment performance report uses the current year as the default
timeframe. The price on January 1st is the one you have to compare to.
On Tue, Nov 26, 2013 at 1:59 AM, William H. Haller wrote:
> Well, yes. If I adjust the time frame I can in theory limit some of the
> badness in the report
Well, yes. If I adjust the time frame I can in theory limit some of the
badness in the reports of investment performance - but who in the world
wants to look up stock purchase and sell dates and then tweak the date
parameters for a particular security just to get the right performance
informati
15 matches
Mail list logo
