[kmymoney] [Bug 450627] error on price update for investment
https://bugs.kde.org/show_bug.cgi?id=450627 --- Comment #6 from Fred --- (In reply to Thomas Baumgart from comment #5) > Please update the AppImage from > https://binary-factory.kde.org/view/AppImage/job/KMyMoney_Release_appimage- > centos7/. It really looks that yours does not contain the aforementioned kio > fix. It > (https://invent.kde.org/packaging/craft-blueprints-kde/-/merge_requests/311) > was only merged in January 2022. In case your version ran fine in another > environment, it probably picked up the kioslave from the installed system. > And, since we're at it, that problem already existed in the old build system > as well but was never fixed AFAIR. I downloaded and run the appimages as suggested and it appears that the problem is gone. Price update works now. Thanks -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 450627] error on price update for investment
https://bugs.kde.org/show_bug.cgi?id=450627 --- Comment #4 from Fred --- s I mentioned before I'm running APPImage 5.1.2-657dbcf2f from approx. Nov/Dec 2021, PS I did some price updates in a test environment before. - same appimage -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 450627] error on price update for investment
https://bugs.kde.org/show_bug.cgi?id=450627 --- Comment #2 from Fred --- running Appimage 5.1.2.657dbcf2f -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 450627] error on price update for investment
https://bugs.kde.org/show_bug.cgi?id=450627 Fred changed: What|Removed |Added CC||d...@email.com --- Comment #1 from Fred --- Created attachment 146983 --> https://bugs.kde.org/attachment.cgi?id=146983&action=edit investment details -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 450627] New: error on price update for investment
https://bugs.kde.org/show_bug.cgi?id=450627 Bug ID: 450627 Summary: error on price update for investment Product: kmymoney Version: 5.1.2 Platform: Appimage OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kmymoney-devel@kde.org Reporter: d...@email.com Target Milestone: --- Created attachment 146982 --> https://bugs.kde.org/attachment.cgi?id=146982&action=edit price update fails SUMMARY While trying to get a price update of a mutual fund from Yahoo I receive an error (see attached screenhots *** STEPS TO REPRODUCE 1. Menu Tools - Update Stock and Currency Price 2. Select date from: 2021-12-15 3. Select Date to: 2022-02-22 3. Update All OBSERVED RESULT price update failed EXPECTED RESULT Price update to be succesful SOFTWARE/OS VERSIONS Linux: Linux Mint 20.3 - CInnamon 5.2.7 KDE Plasma Version: KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 447621] New: after completing a transaction in the ledger, go by default to first field of the same transaction - skip the need of 'New' button
https://bugs.kde.org/show_bug.cgi?id=447621 Bug ID: 447621 Summary: after completing a transaction in the ledger, go by default to first field of the same transaction - skip the need of 'New' button Product: kmymoney Version: 5.0.8 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: ux-ui Assignee: kmymoney-devel@kde.org Reporter: d...@email.com Target Milestone: --- SUMMARY I respectfully suggesting the following improvement: After completing a transaction, to bypass the need to hit the 'new' button for the next transaction. Using the same template (type of transaction) as the previous one. This would speed up the entering of transactions when processing a stack of 'receipts' (Quicken is using this flow) *** SOFTWARE/OS VERSIONS OS: Linux Mint v 20.1 KMyMoney V. 5.0. KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 446566] Automatically remove tags from transaction when they are about to be deleted
https://bugs.kde.org/show_bug.cgi?id=446566 --- Comment #17 from Fred --- (In reply to Jack from comment #16) > I'm not sure how to make that more obvious in the UI (any other thoughts or > suggestions?) but I'll see about emphasizing it in the handbook. > > The issue is that if you hit "OK" you are accepting the current state of the > entire transaction, but you have not yet accepted the change to that > particular split. Jack, maybe 'ok' should be disabled until you have confirmed or cancelled the imminent changes. Fred -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 446566] Automatically remove tags from transaction when they are about to be deleted
https://bugs.kde.org/show_bug.cgi?id=446566 --- Comment #15 from Fred --- (In reply to Jack from comment #14) > *(&^&^( I wrote a whole reply, but got a "mid-air collision" and closed too > quickly before telling it to post anyway. So > I have been unable to replicate the issue, either with a version compiled > from git head of the 5.1 branch, or with the ArtixLinux 5.1.2 version. > > First, I hope you meant "thread" instead of "threat." :-) > > Second, can you check/confirm all the detailed steps you took? After > hitting the X to remove the tag, you need to click the check to accept the > changes to that split. Then you need to click OK to accept the changes to > the transaction. Just hitting "Enter" will Cancel instead of OK. > If you actually did all that, and the tag is not removed, then can you > create a small kmy file that shows the problem? Since you demonstrate the > problem with two different versions, I'd like to see if the problem might be > in the data, although I can't think of how that could work. Specifically, > can you create new transactions that demonstrate the problem? Does it only > happen with multiple splits? (So far, I've only tried with two splits.) Jack, finally the mystery is resolved. Previously I DID NOT hit the 'confirm' action button (√) and went straight to 'OK'. Somehow I ignored this step. Having said that, IMHO, this 't h r e a d' can now be closed. Thanks for your patience. PS: When the a user made changes in the item, perhaps these action button could be more eye-catching, e.g. through a coloured border around them. This way, stupid users, like me, would see better what their have to do ;-) (nice improvement) -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 446566] Automatically remove tags from transaction when they are about to be deleted
https://bugs.kde.org/show_bug.cgi?id=446566 --- Comment #13 from Fred --- Created attachment 144659 --> https://bugs.kde.org/attachment.cgi?id=144659&action=edit Split transaction, delete flase tag entry, KMM v 5.1.2-94 - Just as FYI no action button 'x' on tag of a split transaction visible. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 446566] Automatically remove tags from transaction when they are about to be deleted
https://bugs.kde.org/show_bug.cgi?id=446566 --- Comment #12 from Fred --- Created attachment 144658 --> https://bugs.kde.org/attachment.cgi?id=144658&action=edit Split transaction, delete flase tag entry, KMM v 5.0.8 the delete 'action button' is visible but has no effect after saving back the whole transaction. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 446566] Automatically remove tags from transaction when they are about to be deleted
https://bugs.kde.org/show_bug.cgi?id=446566 --- Comment #11 from Fred --- (In reply to Jack from comment #10) > You didn't widen the column enough. If you make it even wider, the X for > men's undies should appear, where currently only the X for RBC MC is > showing. The down arrow lets you select additional tags. The text to the > left of that just shows the currently selected tags. Each selected tag > should appear with an X, but to the right of the down arrow. Jack, I apologize that this becomes a long winding threat, but the fact is, I widened the column wide enough, you can see both tags with the accompanying 'x'. When hitting the 'mens undies' entry's 'x', confirm the change with 'ok' and save the whole transaction, nothing is changing in the transaction. For clarity, I upload 2 screenshots, one from v 5.08 and the other one from v 5.1.2-94 (which is even more odd). Don't know what else I could test. Cheers Fred -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 446566] Automatically remove tags from transaction when they are about to be deleted
https://bugs.kde.org/show_bug.cgi?id=446566
--- Comment #9 from Fred ---
Created attachment 144407
--> https://bugs.kde.org/attachment.cgi?id=144407&action=edit
widened tag column after 'X' on false entry
It appears that the false tag entry ('men undies') will be removed from the
split transaction through 'X'. However, when confirmed and saved, it's still
there - ^confused^
--
You are receiving this mail because:
You are the assignee for the bug.
[kmymoney] [Bug 446566] Automatically remove tags from transaction when they are about to be deleted
https://bugs.kde.org/show_bug.cgi?id=446566 --- Comment #8 from Fred --- (In reply to Thomas Baumgart from comment #6) > Try to widen the tag column in the split editor. I agree, it makes a > difference if you have a split transaction or a normal one. I tried to > duplicate your problem with the latest stable version (5.12.) and have no > problems to a) remove the tag from the split and b) delete the tag > afterwards. Chances are that the problem has been fixed in the meantime. Thomas: I widened the column and when I click on the 'X' it appears that it would delete the false tag entry (see new screenshot) However when I confirm the changes (OK button), save the transaction and open it for edit again, it's still there. Was the bug reported before so that it got fixed? Thanks Fred -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 446566] Automatically remove tags from transaction when they are about to be deleted
https://bugs.kde.org/show_bug.cgi?id=446566 --- Comment #7 from Fred --- (In reply to Jack from comment #5) > Please be a bit more specific about why you can't remove the tag. What > happens when you click on the "X" to the left of "mens undies"? Hi Jack, I can't be more specific. What happens when I click on the 'X" : Nothing. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 446566] Automatically remove tags from transaction when they are about to be deleted
https://bugs.kde.org/show_bug.cgi?id=446566 --- Comment #4 from Fred --- Created attachment 144359 --> https://bugs.kde.org/attachment.cgi?id=144359&action=edit split items with false tag entries. I can't remove the false tag entries (here: 'men undies'. THe entry 'RBC MC' would be the correct tag but I can't remove either. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 446566] Automatically remove tags from transaction when they are about to be deleted
https://bugs.kde.org/show_bug.cgi?id=446566 --- Comment #3 from Fred --- (In reply to Thomas Baumgart from comment #1) > Created attachment 144341 [details] > Button to be pressed to remove tag from transaction > > The error message states, that you cannot remove a tag that is still in use. > First remove it from the/all transaction/s by pressing the "remove icon" > next to the tag's text when editing a transaction (see attached screenshot). > Save the transaction. Once all references are removed, you can delete the > tag from the list. Hi Thomas, in my version of KMM I don't see an 'x' button on the 'main' window of the transaction. Perhaps because this an entry with split items. When I open the split items and select the item in question, In can see the two tag entries listed with an 'x', however I can't delete one or both tags from the item. (see attached screenshot) -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 446566] New: cannot delete false tag entry.
https://bugs.kde.org/show_bug.cgi?id=446566 Bug ID: 446566 Summary: cannot delete false tag entry. Product: kmymoney Version: 5.0.8 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-devel@kde.org Reporter: d...@email.com Target Milestone: --- Created attachment 144280 --> https://bugs.kde.org/attachment.cgi?id=144280&action=edit screenshot 'deleting tag entry' SUMMARY During a transaction with split items I entered in the tag field a text that supposed to be the memo text as well as a valid tag. I tried to correct the mistake in the tag field but was not able to edit the contents successfully or to clean the whole field contents. I saved the transaction. Select the 'tag' section in the menu to edit the listed tags. I tried to delete the aforementioned 'wrong' tag value. It responds with a message "unable to remove tags" (see attached png) *** STEPS TO REPRODUCE 1. Entered a transaction with split items 2. enter in the tag field an random value e.g. 'abcd'. 3. add another 'valid' tag 4. conform the items on the spli list 5. save transaction 6. go to menu entry 'tags' 7. select form the listed tags the entry showing 'abcd' 8. select the 'delete' action button 9. it should deny the deletion of the tag entry OBSERVED RESULT did not delete the entry 'abcd' form the tag field in the split transaction Did not delete the tag with the value 'abcd' EXPECTED RESULT to be able to edit (or to cleanout) the tag field on a split transaction to be able to delete the falsely created tag (abcd) SOFTWARE/OS VERSIONS Linux/Cinnamon KDE Plasma Version: KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 441322] 'ghost' font when renaming a category
https://bugs.kde.org/show_bug.cgi?id=441322 --- Comment #5 from Fred --- Hi Jack I downloaded and launched the latest AppImage version (KMyMoney-5.1.2-94d7cf5-x86_64.AppImage). I appears that in the new version the layout of the edit window has changed (there is no 'Ren' button anymore). After right-mouse click of the particular category I can select the "rename" mode and there is not ghost font anymore. What puzzles me is that when I'm now launching the 'old' version (5.0.8) the behaviour is now the same as in the 5.1.2 version. But that's fine with me. I just have to embed the new version in my menu system. It seems that the problem is resolved now. A for now I will not test the old version with a new user as you've suggested. Thanks for your help. Fred -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 441322] 'ghost' font when renaming a category
https://bugs.kde.org/show_bug.cgi?id=441322 --- Comment #3 from Fred --- (In reply to Thomas Baumgart from comment #1) > Created attachment 140936 [details] > Showing the same on stock openSUSE 15.2 > > Could it be, that this is caused by the combination of your local > components? I don't see this problem here with a standard KDE install on the > breeze theme. I have no way of knowing whether or even which local components can influence the outcome. I don't know the source code of kmymoney :-( -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 441322] New: 'ghost' font when renaming a category
https://bugs.kde.org/show_bug.cgi?id=441322 Bug ID: 441322 Summary: 'ghost' font when renaming a category Product: kmymoney Version: 5.0.8 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-devel@kde.org Reporter: d...@email.com Target Milestone: --- Created attachment 140921 --> https://bugs.kde.org/attachment.cgi?id=140921&action=edit screenshot with 'ghost' font (PNG) SUMMARY When renaming a category, after put focus on the name field, the contents shows a 'ghost' font over a a green background colour. This makes it very difficult to determine on which position I'm on in the name field. It also would be nice to have the field cleared for e.g. through the backspace key. STEPS TO REPRODUCE 1. select an existing category 2. click button 'Ren' 3. set focus on the field with the cursor/mouse OBSERVED RESULT a 'ghost' font in the field EXPECTED RESULT clean font, easy to read. SOFTWARE/OS VERSIONS System:Kernel: 5.4.0-81-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 4.8.6 wm: muffin dm: LightDM Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focalasma: ADDITIONAL INFORMATION see attached screenshot -- You are receiving this mail because: You are the assignee for the bug.
