[kmymoney] [Bug 469431] Need better way to handle changes in stock price quote source
https://bugs.kde.org/show_bug.cgi?id=469431 --- Comment #53 from Ralf Habacker --- For yahoo(In reply to Ralf Habacker from comment #52) > It might be a better approach to use a csv download if available, there is > not that much that can change. For yahoo.com this is https://query1.finance.yahoo.com/v7/finance/download/%1-%2?events=history&includeAdjustedClose=true -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 469431] Need better way to handle changes in stock price quote source
https://bugs.kde.org/show_bug.cgi?id=469431 --- Comment #52 from Ralf Habacker --- It might be a better approach to use a csv download if available, there is not that much that can change. For fx-rate that would be https://fx-rate.net/historical/?c_input=%1&cp_input=%2&csv=true -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 479451] net zero split transactions: split values change sign when edited
https://bugs.kde.org/show_bug.cgi?id=479451 josephosw...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||kmymoney-master-3014-linux- ||gcc Status|REPORTED|RESOLVED --- Comment #3 from josephosw...@gmail.com --- I can confirm that a recent build kmymoney-master-3014-linux-gcc-x86_64.AppImage with the deposit/payment split fixes this issue. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 469431] Need better way to handle changes in stock price quote source
https://bugs.kde.org/show_bug.cgi?id=469431 --- Comment #51 from jesse --- Created attachment 165114 --> https://bugs.kde.org/attachment.cgi?id=165114&action=edit Example of a successful update with the configs mentioned Here is an example of the success message I received with these settings. I placed a link to the location of the online forum where I found the settings. I did not come up with them myself but can say that they worked for me on Kmymoney version: Version 5.1.3-0663fcc7b (Find KMM version , Toolbar > Help > About KMyMoney) I also agree that the average user does not know about compilations, or other tools methods that developers use. I think those suggestions are offered in case the user does know but if the user does not know, then the people here are very open to helping them walk through it. I've been helped in the past and am very grateful. If the user does not want to mess with it, then usually the answer is, wait until it is fixed. (At times the user is provided a link to a newer unreleased version that may include the fix they need, if available) I think the suggestions of compiling and others are only in case the user know how to do it. Much like when the mechanic explains what needs to be done. If you ask them, they may share details on how to do it in case you want to try yourself. But to the point, most people do not want to try because they usually do not have the knowledge or the tools to try it. Not their realm of expertise. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 469431] Need better way to handle changes in stock price quote source
https://bugs.kde.org/show_bug.cgi?id=469431 --- Comment #50 from jesse --- Created attachment 165113 --> https://bugs.kde.org/attachment.cgi?id=165113&action=edit Image showing the set up for YahooFinance Trying to contribute by driving conversations is fine but I do not think the approach of name calling or any other form of aggression is necessary. Software development is challenging and especially more so when the dev teams are trying to do this on their free time and as volunteers. No developer wants it to be any harder than it needs to be. I believe the team here has mentioned that perhaps the real bug is the missing the documentation on how to leverage the tool to fix the online quotes. Maybe there should be a bug ticket open on that subject. Meanwhile, I am attaching a screenshot of my set up for YahooFinance. -- You are receiving this mail because: You are the assignee for the bug.
