SUMMARY Thank you for the change to be able to create sub-categories directly in the ledger view in Bug 514987. The changes are working well. However, there does appear to me to be a small inconsistent behaviour. Others may disagree. When in the account ledger, if for an entry I start typing in the "Category" box it does a case insensitive match to category names that already exist. So for example, if there is an existing "Insurance" category, both "Insurance" and "insurance" will match this in the drop down list that appears. This also happens when I first start to create a new sub-category of "Cycle Insurance" under "Insurance". However, if I have typed "insurance" and then go on typing "insurance:Cycle Insurance" I get a pop-up box error with the text: "The selected parent account insurance does not exist in the Expense hierarchy". Which of course is strictly correct. Everything does of course works as expected if I enter "Insurance:Cycle Insurance". Would it make sense for the check for an existing Category name to be case insensitive in the case when a new sub-category is being created? STEPS TO REPRODUCE 1. Have a KMyMoney data file with an existing "Insurance" category 2. In an account ledger view, for an account entry, in the "Category" box type "insurance". KMyMoney does a case-insensitive match. 3. Now continue typing to create the desired new sub-category, for example "insurance: Cycle Insurance" OBSERVED RESULT A pop-up box error will appear with the text: "The selected parent account insurance does not exist in the Expense hierarchy". EXPECTED RESULT KMyMoney should use a case insensitive match when checking for an existing "Insurance" category when creating a new "sub-category". SOFTWARE/OS VERSIONS Windows: 10 Linux: Ubuntu 2024.04.3 AppImage ADDITIONAL INFORMATION