[kmymoney] [Bug 426400] Fix KF5 issues on Windows
https://bugs.kde.org/show_bug.cgi?id=426400 Bug 426400 depends on bug 460007, which changed state. Bug 460007 Summary: Forecasting graph on the home page has random quality problems https://bugs.kde.org/show_bug.cgi?id=460007 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 460007] Forecasting graph on the home page has random quality problems
https://bugs.kde.org/show_bug.cgi?id=460007 Ralf Habacker changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #21 from Ralf Habacker --- (In reply to Dawid Wróbel from comment #15) > Processed home view section 8 in 9145 ms This issue, which was present before, is now traceable due to the changes made to this ticket, but is independent of the adjustments made for this ticket. A separate ticket should be created for this. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 460007] Forecasting graph on the home page has random quality problems
https://bugs.kde.org/show_bug.cgi?id=460007 --- Comment #22 from Dawid Wróbel --- > This issue, which was present before, is now traceable due to the changes > made to this ticket, but is independent of the adjustments made for this > ticket. A separate ticket should be created for this. I am not convinced, tbh. Yes, the underlying issue is slowness of the home view processing, but the frequency of rewriting the window increased to the point that resizing renders the app unusable is, in my opinion, a side effect that is not otherwise easily fixable and, arguably, a no lesser of an issue than the graph being rendered improperly. This fix effectively creates another big issue and I stand by my initial point that it's best not to touch home view altogether, as it is full of spaghetti code of which any modification can cause several other side effects that are hard to trace. I am saying as the author of its migration form WebEngine and if I was to do this again, I would instead just rewrite it from scratch using QML and never look back :) -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 460007] Forecasting graph on the home page has random quality problems
https://bugs.kde.org/show_bug.cgi?id=460007 --- Comment #23 from Dawid Wróbel --- (to clarify, I don't have a problem with this bug being fixed the way it was, just making sure we are on the same page regarding how badly that home page code needs rewriting) -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 362263] OFX import transactions inherit split from preexisting transaction
https://bugs.kde.org/show_bug.cgi?id=362263 Justin Zobel changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from Justin Zobel --- Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 418479] Historical Investment Transactions causes crash
https://bugs.kde.org/show_bug.cgi?id=418479 --- Comment #12 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
