Bug 344619

Summary: Allow keyboard and mouse navigating on ALL the scheduled transactions in the ledger view
Product: [Applications] kmymoney Reporter: J Kerckhofs <jimmy.kerckhofs>
Component: generalAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: CONFIRMED ---    
Severity: wishlist CC: jimmy.kerckhofs, onet.cristian
Priority: NOR    
Version: 4.7.1   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: All   
Latest Commit: Version Fixed In:

Description J Kerckhofs 2015-02-27 09:06:21 UTC
Keyboard/Mouse navigation is bound to the fact that an item can be selected or not, when you reach the first scheduled entry which can't be selected the selection will go back to the first schedule which can be selected; if you ask why only the first few scheduled entries can be selected the explanation is that scheduled transaction instances must be entered in the order of their occurrence. For example if I have a monthly transaction due on 28.02.2015 although I can see the entry on 28.03.2015 I can't enter it until the occurrence due on 28.02.2015 is entered.

Reproducible: Always

Steps to Reproduce:
1. Set up month scheduled transactions
2. Configure the scheduled transactions to see a forecast off 360 days in the ledger
3. Move with the ARROW DOWN / PG DOWN keyboard buttons over the forecast transactions, try to navigate to the next months
4. The active row jumps back to the first occurrence off the scheduled transaction


Expected Results:  
Moving down in the grid instead off jumping back to the first occurrence.

I have the scheduled transactions visible in my ledger with a 1 year forecast. This allows me to see for every month what is the potential extra saving, and create a one off scheduled transaction for each month, one for each month with all different amounts, and set the date to the beginning off that month, This allows me to book an amount to my savings account directly after we receive our salaries. This works great for me. However the input in KMyMoney could be better, navigating with arrows/PGDN in the ledger on the forecast transactions doesn't work, works only for the first occurrences.