Interface bugs and inconsistencies in QB Mac 2024
Kind of shocked how many bugs I've run into with the current version (V23.0.2 R3 Build 518), and I'm frankly kind of insulted that it's no longer possible to buy permanent licenses when longstanding bugs and poor interface performance (many of these have been around since at least 2014).
Just had a reproducible bug that beach-ball's the application. Having a split open in a register that does *not* have enough transactions to require a scroll bar, and recording the transaction, will beachball the application completely. Closing the split and recording behaves properly.
Could be related, though I've never figured out what triggers it, to a very annoying bug that redraws registers where the columns are temporarily mis-set so that only "Payment" and "Deposit" are visible, but "Balance" is either completely out of the window or partially draws past the window's bounds - scrolling in the register resets it, but this regularly happens to me when I'm doing things that are not actually involving the register in question.
Highlighting a transaction in the register for some reason alters cell padding so the highlighted transaction's date and account fields suddenly wrap, meaning the year is now cut off, and if you have hierarchical accounts and spaces in account names, things become near-impossible to readily determine - particularly aggravating with inconsistent auto-complete on accounts. EG; if the account is "My Bank:Checking", unhighlighted it might say "My Bank:Check...", but on highlighting you'll only see "My" because it hard wraps on the space and treats "Bank:Checking" as a new wrap word.
Auto-complete generally is obnoxious - Do you type "American Express" a lot? Better hope you don't have a single transaction somewhere to "American Business", because you'll never be able to get away with typing "Am" and getting the most-likely result.
WHY does the credit card charge importer (and the CC charge window for the primary transaction) not permit entering memos??! This makes zero sense. The transactions can *have* memos, as exhibited by the fact that the register and split view in the charge window allows entering them, but why do I have to write my own IIF formatter in order to finagle copying/pasting spreadsheet data into QB *with memos*?!
Rant over.
