[kmymoney] [Bug 366492] OFX Import dialog does not import OFX files

2018-01-09 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=366492 Thomas Baumgart changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED

[kmymoney] [Bug 366492] OFX Import dialog does not import OFX files

2018-01-08 Thread Ralf Habacker
https://bugs.kde.org/show_bug.cgi?id=366492 Ralf Habacker changed: What|Removed |Added Version|unspecified |git (master) CC|

[kmymoney] [Bug 366492] OFX Import dialog does not import OFX files

2017-08-05 Thread Alexandre
https://bugs.kde.org/show_bug.cgi?id=366492 --- Comment #5 from Alexandre --- Thomas, thanks for the correction, that statement is redundant. I was debugging some seg fault and changed this function a few times and forced that initialization to check and forgot to remove it. -- You are receivin

[kmymoney] [Bug 366492] OFX Import dialog does not import OFX files

2017-08-05 Thread Thomas Baumgart
https://bugs.kde.org/show_bug.cgi?id=366492 --- Comment #4 from Thomas Baumgart --- Alexandre, thanks for the proposed patch. I'll take care of it. I just wonder what the following change is needed for: - QString accId; + QString accId = QString(); The additional assignment does not make any

[kmymoney] [Bug 366492] OFX Import dialog does not import OFX files

2017-08-04 Thread Alexandre
https://bugs.kde.org/show_bug.cgi?id=366492 --- Comment #3 from Alexandre --- KF5 seems to have changed the API to select files and the capability of importing OFX is commented on the code. This patch allows a single file to the imported, f more than one is selected only the first one is imported

[kmymoney] [Bug 366492] OFX Import dialog does not import OFX files

2017-08-04 Thread Alexandre
https://bugs.kde.org/show_bug.cgi?id=366492 Alexandre changed: What|Removed |Added CC||alexandre...@gmail.com --- Comment #2 from Alexandr

[kmymoney] [Bug 366492] OFX Import dialog does not import OFX files

2017-04-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=366492 --- Comment #1 from tam...@gmail.com --- This exact behavior is seen in b1468e678e5fc0a4092c11b63c3e5255f4659a8c -- You are receiving this mail because: You are the assignee for the bug.