[kmymoney] [Bug 493802] OS 4k display scaling 200% fails on home page
https://bugs.kde.org/show_bug.cgi?id=493802 Jack changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Version Fixed In||5.2 Status|NEEDSINFO |RESOLVED --- Comment #12 from Jack --- This is now getting away from bugs and towards user support and usage issues. Please work through these on Discuss or the mailing list or other location listed at https://kmymoney.org/support.html. Thanks for understanding. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 493802] OS 4k display scaling 200% fails on home page
https://bugs.kde.org/show_bug.cgi?id=493802 --- Comment #10 from Pete --- Again in the master, I just noticed that home page future payments for credit cards now generate 2 rows rather than one. Very confusing. The schedule name (credit card) and account (chequing) appear as before with the amount in red as before. The "duplicate" useless new row shows the schedule name (credit card) and account (credit card) with the same amount but in black. Please filter this out, it is seriously confusing and counter productive. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 493802] OS 4k display scaling 200% fails on home page
https://bugs.kde.org/show_bug.cgi?id=493802 --- Comment #9 from Pete --- With the master, quotes no longer work for Currency and Yahoo Finance. Could you please provide the required updates or just issue a revised master? Thanks. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 493802] OS 4k display scaling 200% fails on home page
https://bugs.kde.org/show_bug.cgi?id=493802 --- Comment #11 from Pete --- Again in the master, the stock quote screen does not remember its resizing. It always reverts back to a too-small screen. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 493449] Crash when editing and reconciling entries in ledger
https://bugs.kde.org/show_bug.cgi?id=493449 --- Comment #2 from Petr Kadlec --- (In reply to Jack from comment #1) > Have you tried to complete the reconciliation? #5 in the traceback is > called when you are done editing a transaction (usually by clicking OK or > cancel.) Yes, after the crash, I restarted kmymoney and redid everything I wanted to do. Unfortunately, I can’t say which _exact_ operations I did prior to the crash. > If you can edit several transactions without a crash, it's > unlikely we can find the actual cause. Yeah, I understand that, unless the stack trace hints to a specific issue, I’m afraid I am unable to provide more info. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 493802] OS 4k display scaling 200% fails on home page
https://bugs.kde.org/show_bug.cgi?id=493802 --- Comment #3 from Pete --- When you highlight a row other than the last one (most recent) in an account's register, then minimize the KMM software, then un-minimize, the selected row in no longer highlighted. It is the last one that acquires the highlight. This is a real productivity buster. You need to review how KMM behaves in a 4k environment. It has very obviously not been tested under these conditions. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 493802] OS 4k display scaling 200% fails on home page
https://bugs.kde.org/show_bug.cgi?id=493802 --- Comment #4 from Jack --- I'll be glad to test if you want to buy me a 4K monitor :-) The developers can only test on equipment they have. I recall we've had issues reported on hi-dpi displays, and it's possible that's the actual issue, rather than the actual screen resolution. I'll see if I can try testing with scaling on a smaller monitor - it might also show the problem. Regarding losing focus after minimizing, I just confirmed that behavior on a non-4k screen under Xorg with 5.1, but apparently fixed in master branch. If your original issue is still present in master branch, then it would really help if you could test on Xorg, and if you could test other KDE programs. (See https://kmymoney.org/download.html for how to get an Appimage version compiled from git master branch.) -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 493802] OS 4k display scaling 200% fails on home page
https://bugs.kde.org/show_bug.cgi?id=493802 --- Comment #5 from danfran...@gmail.com --- Hello, can you specify what version of app and KDE plasma are using? PS. Try updating -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 493802] OS 4k display scaling 200% fails on home page
https://bugs.kde.org/show_bug.cgi?id=493802 --- Comment #6 from Pete --- I am not sure I fully understand your jargon. The AppImage at your link provided above is what I have been using for months (version 3218). Is this what you call master branch? I can try booting my Ubuntu 22.04 LTS with Xorg, if you wish. I will report back later this afternoon on this test. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 493802] OS 4k display scaling 200% fails on home page
https://bugs.kde.org/show_bug.cgi?id=493802 --- Comment #7 from Pete --- I am so busy I did not bother to read to the end of the page, sorry about that :-) The master (version 3536) eliminates the scaling problem and the register focus problem with default Ubuntu 22.04 LTS. However, on the home page, in the liability accounts at the very top, the amounts that were always in red are now in black. Please fix. Thanks. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 493802] OS 4k display scaling 200% fails on home page
https://bugs.kde.org/show_bug.cgi?id=493802 --- Comment #8 from Jack --- Sorry for any confusing terminology. When reporting the version you are using, it helps state what Help/About KMyMoney says. In this case, it wouldn't have actually mattered, but the full version would have told us you were using the Appimage and not a version released by the distribution. (You would have to include that in the report, as the dropdown for versions does include "git(master)" but not a way to say git(stable) or git(5.1). Code development is done in git, in which there are different "branches" which allows multiple lines of development to be tracked. The 5.1 branch has the code for 5.1.3, and includes bug fixes. The Appimage versions compiled from the code in the 5.1 branch will have versions like kmymoney 5.1.3-eef04f1 where that last bit shows the exact "commit" (specific change) included. The "master" branch includes additional bug fixes, plus new features. In this case, one of the major changes is a major rewrite of the ledger code. Versions from master branch look like kmymoney 5.1.80-fd13f44. The code from master branch will be released as 5.2, but there is not yet a definite timeline for that. Given that your two main problems have been addressed there, I will close this as resolved in 5.2. Although using master branch is labelled as experimental, there are multiple folks who have been using it for their day-to-day work. The only special advice is be sure to keep good backups. I'm not absolutely certain, but I believe that the change of display color for the balance of liability accounts is intentional. Since they are LIABILITY accounts, a positive amount (shown in black) is what you owe. While you could open a wishlist bug requesting it be changed back, or made a configuration choice, I do not suspect it will get much priority. -- You are receiving this mail because: You are the assignee for the bug.
