Bug 235882

Summary: Optimize the performance of the register when a lot of transactions are displayed (orig. name Sluggish performance when navigating in ledger view using cursor keys)
Product: [Applications] kmymoney Reporter: Thomas Baumgart <tbaumgart>
Component: generalAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: RESOLVED FIXED    
Severity: wishlist CC: diacobel, mfcarpino
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:

Description Thomas Baumgart 2010-05-01 08:10:59 UTC
Version:           SVN HEAD (using KDE 4.3.5)
OS:                Linux
Installed from:    openSUSE RPMs

When the transaction form is turned off, using the cursor keys to navigate from one transaction to the next/previous is very (I mean *very*) slow. 

The responsiveness is better when the transaction form is turned on.
Comment 1 Cristian Oneț 2010-05-01 09:22:41 UTC
I didn't notice any difference between the two modes (with/without the transaction form) and keyboard navigation in both works OK, no performance issues here.
Comment 2 Cristian Oneț 2010-05-03 21:52:40 UTC
Any news on this?
Comment 3 Cristian Oneț 2010-05-09 09:40:02 UTC
I've received your anon file and if all the transactions are shown (even the reconciled ones) there is a performance issue when navigating with the keyboard. The same issue is when selecting an item with the mouse but I think that it's not that visible because the user can't click with the mouse that fast (on different transactions).
The problem is that on each selection change the whole register is updated (Register::updateRegister is called) and I wouldn't like to touch that part right now (we've got a release next Saturday).
That's why I'm changing this to a wish to optimize the performance of the register with a lot of transactions (since you can get decent performance by hiding reconciled transactions).
Comment 4 Alvaro Soliverez 2010-08-29 15:49:56 UTC
*** Bug 249401 has been marked as a duplicate of this bug. ***
Comment 5 Michael Carpino 2018-03-01 15:25:29 UTC
Enhancement requested over 5 years ago.  Bug closed.  Response using cursor is no longer slow.