another weird bug
Hello, If this is already fixed in master I apologize. I haven't rebuilt kmymoney in a few weeks. But I hit something and thought it was worth mentioning at least here to check. I'll file a bug if it's not known after I rebuild and make sure it's still happening. When I enter a new transaction and enter a payee with the wrong case (In my case typing "myriam" instead of "Myriam" a popup comes up asking if I want to add Myriam to the list of payees even though that casing is already an existing payee. It seems the case is getting fixed after it has checked for an existing payee, but before it shows the popup asking if I want to add. BR, Jeremy
Re: another weird bug
On 2023.10.19 14:02, Jeremy Whiting via KMyMoney-devel wrote: Hello, If this is already fixed in master I apologize. I haven't rebuilt kmymoney in a few weeks. But I hit something and thought it was worth mentioning at least here to check. I'll file a bug if it's not known after I rebuild and make sure it's still happening. When I enter a new transaction and enter a payee with the wrong case (In my case typing "myriam" instead of "Myriam" a popup comes up asking if I want to add Myriam to the list of payees even though that casing is already an existing payee. It seems the case is getting fixed after it has checked for an existing payee, but before it shows the popup asking if I want to add. BR, Jeremy I can confirm - still present in git head master (unless someone snuck in a fix in the past day.) Rather than saying the case gets fixed, I'd say it is matching to an existing payee using case insensitive matching, but then not recognizing it is using the existing payee. Still a bug. However, if it offers one or more transactions to use as a template for the new transaction, and you pick one of them, it uses the existing payee. (That seems OK.) On the other hand, if you say "Yes" to creating the new Payee, it creates one with the same capitalization as the existing one, with "[1]" appended, instead of adding a new payee with the different capitalization as just entered. I think Payees should be unique (case insensitive,) although I suppose that could be debated. In any case, filing a bug makes sense, as the behavior does need to change. Jack
Re: another weird bug
Ok, will do. Thanks for confirming. On Thu, Oct 19, 2023 at 1:35 PM Jack via KMyMoney-devel < kmymoney-devel@kde.org> wrote: > On 2023.10.19 14:02, Jeremy Whiting via KMyMoney-devel wrote: > > Hello, > > > > If this is already fixed in master I apologize. I haven't rebuilt > > kmymoney > > in a few weeks. But I hit something and thought it was worth > > mentioning at > > least here to check. I'll file a bug if it's not known after I > > rebuild and > > make sure it's still happening. > > > > When I enter a new transaction and enter a payee with the wrong case > > (In my > > case typing "myriam" instead of "Myriam" a popup comes up asking if I > > want > > to add Myriam to the list of payees even though that casing is > > already an > > existing payee. It seems the case is getting fixed after it has > > checked for > > an existing payee, but before it shows the popup asking if I want to > > add. > > > > BR, > > Jeremy > > > I can confirm - still present in git head master (unless someone snuck > in a fix in the past day.) > > Rather than saying the case gets fixed, I'd say it is matching to an > existing payee using case insensitive matching, but then not > recognizing it is using the existing payee. Still a bug. However, if > it offers one or more transactions to use as a template for the new > transaction, and you pick one of them, it uses the existing payee. > (That seems OK.) On the other hand, if you say "Yes" to creating the > new Payee, it creates one with the same capitalization as the existing > one, with "[1]" appended, instead of adding a new payee with the > different capitalization as just entered. > > I think Payees should be unique (case insensitive,) although I suppose > that could be debated. In any case, filing a bug makes sense, as the > behavior does need to change. > > Jack >
[kmymoney] [Bug 475841] New: payees with different case not recognized until asking
https://bugs.kde.org/show_bug.cgi?id=475841 Bug ID: 475841 Summary: payees with different case not recognized until asking Classification: Applications Product: kmymoney Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ux-ui Assignee: kmymoney-devel@kde.org Reporter: jpwhit...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** If you enter a new transaction, but type the payee with slightly different case a popup asks if you want to add a new payee (but already has any existing payee's case in the question). If you click Yes, it adds a new payee with [1] at the end of the name. STEPS TO REPRODUCE 1. Enter a transaction with an existing payee with one letter case changed. I.e. bank instead of Bank 2. Watch when the gui asks if you want to add "Bank" as a new payee. 3. Click Yes OBSERVED RESULT "Bank [1]" added to the list of payees. EXPECTED RESULT Either or both of: 1. Bank payee left alone, no new payee added. 2. bank corrected to Bank and no question about payee asked. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: Plasma6 built from git KDE Frameworks Version: KF5 from arch packages, 5.110.0-1 currently Qt Version: 5.15.11-1 from arch packages. ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
Re: another weird bug
https://bugs.kde.org/show_bug.cgi?id=475841 filed. Thanks again, if I'm able to get master built again I'll take a stab at it, but it's there in case I don't get back to it. On Thu, Oct 19, 2023 at 1:40 PM Jeremy Whiting wrote: > Ok, will do. Thanks for confirming. > > On Thu, Oct 19, 2023 at 1:35 PM Jack via KMyMoney-devel < > kmymoney-devel@kde.org> wrote: > >> On 2023.10.19 14:02, Jeremy Whiting via KMyMoney-devel wrote: >> > Hello, >> > >> > If this is already fixed in master I apologize. I haven't rebuilt >> > kmymoney >> > in a few weeks. But I hit something and thought it was worth >> > mentioning at >> > least here to check. I'll file a bug if it's not known after I >> > rebuild and >> > make sure it's still happening. >> > >> > When I enter a new transaction and enter a payee with the wrong case >> > (In my >> > case typing "myriam" instead of "Myriam" a popup comes up asking if I >> > want >> > to add Myriam to the list of payees even though that casing is >> > already an >> > existing payee. It seems the case is getting fixed after it has >> > checked for >> > an existing payee, but before it shows the popup asking if I want to >> > add. >> > >> > BR, >> > Jeremy >> > >> I can confirm - still present in git head master (unless someone snuck >> in a fix in the past day.) >> >> Rather than saying the case gets fixed, I'd say it is matching to an >> existing payee using case insensitive matching, but then not >> recognizing it is using the existing payee. Still a bug. However, if >> it offers one or more transactions to use as a template for the new >> transaction, and you pick one of them, it uses the existing payee. >> (That seems OK.) On the other hand, if you say "Yes" to creating the >> new Payee, it creates one with the same capitalization as the existing >> one, with "[1]" appended, instead of adding a new payee with the >> different capitalization as just entered. >> >> I think Payees should be unique (case insensitive,) although I suppose >> that could be debated. In any case, filing a bug makes sense, as the >> behavior does need to change. >> >> Jack >> >
