Version: 3.97.2 (using KDE 4.3.5) OS: Linux Installed from: openSUSE RPMs Though the 'enter automatically' button is checked, the scheduled transactions for 1 May did not enter automatically. Right clicking and entering one manually resulted in the second also being entered but its entry being darkened. Right clicking and entering the second manually resulted in the entry showing at normal brightness. Will not be able to replicate for another two weeks until next scheduled transaction.
Having more details about the transaction should help, since I have several schedules my own, and they enter automatically just fine.
On Sunday 02 May 2010 00:47:59 Alvaro Soliverez wrote: > https://bugs.kde.org/show_bug.cgi?id=235880 > > > > > > --- Comment #1 from Alvaro Soliverez <asoliverez gmail com> 2010-05-02 > 01:47:51 --- Having more details about the transaction should help, since > I have several schedules my own, and they enter automatically just fine. > Hi Alvaro I presently have 10 outstanding schedules, 7 bills and 3 deposits. One dates back to 17 Apr., most are monthly, 2 are 4-weekly and one 3-monthly. What else do you need to know? Allan
On Sunday 02 May 2010 00:47:59 Alvaro Soliverez wrote: > https://bugs.kde.org/show_bug.cgi?id=235880 > > > > > > --- Comment #1 from Alvaro Soliverez <asoliverez gmail com> 2010-05-02 > 01:47:51 --- Having more details about the transaction should help, since > I have several schedules my own, and they enter automatically just fine. > Hi Alvaro > I presently have 10 outstanding schedules, 7 bills and 3 deposits. One > dates back to 17 Apr., most are monthly, 2 are 4-weekly and one 3-monthly. > What else do you need to know > Oops Just ignore my last post. I found that the 'enter on startup' option wasn't on, possibly since installing v4. It became involved in another problem, helping to confuse. Allan
John, can you provide more details on these schedules entries? Also, having an anonymized file would help.
Further information as requested. Downloaded latest build from packman. Scheduled transaction for today appears greyed out in ledger even though it is marked for automatic entry Opening the Calendar view in Schedules and selecting Enter in the pop-up enables, via several other popups, the transaction to be entered in the ledger and the account totals updated. I repeated this three times with identical results. john@linux-1kki:~/John> kmymoney KDE https proxy setting is 'HTTPS_PROXY' Setting GWEN_PROXY to '' 7:2010/05/11 11-30-38:aqbanking(5217):started 3:2010/05/11 11-30-38:aqbanking(5217):qbanking.cpp: 422: No Qt translation found for your language en KMyMoney kbanking plugin loaded KMyMoney reconciliation report plugin loaded Calling appendChild() on a null node does nothing. KMyMoney printcheck plugin loaded QFSFileEngine::open: No file name specified KMyMoney ofximport plugin loaded KMyMoney iCalendar plugin loaded reading file start parsing file startDocument QPainter::begin: Widget painting can only begin as a result of a paintEvent QPainter::translate: Painter not active QPainter::setClipRect: Painter not active QPainter::setPen: Painter not active QPainter::worldTransform: Painter not active reading accounts reading transactions reading securities reading prices reading reports endDocument QPainter::begin: Widget painting can only begin as a result of a paintEvent QPainter::translate: Painter not active QPainter::setClipRect: Painter not active QPainter::begin: Widget painting can only begin as a result of a paintEvent QPainter::begin: Widget painting can only begin as a result of a paintEvent QPainter::translate: Painter not active QPainter::translate: Painter not active QPainter::save: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::pen: Painter not active QPainter::setFont: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::restore: Unbalanced save/restore QPainter::translate: Painter not active QPainter::translate: Painter not active QPainter::save: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::pen: Painter not active QPainter::setFont: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::restore: Unbalanced save/restore QPainter::translate: Painter not active QPainter::translate: Painter not active QPainter::save: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::pen: Painter not active QPainter::setFont: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::restore: Unbalanced save/restore QPainter::translate: Painter not active QPainter::translate: Painter not active QPainter::save: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::pen: Painter not active QPainter::setFont: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::restore: Unbalanced save/restore QPainter::translate: Painter not active QPainter::translate: Painter not active QPainter::save: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::pen: Painter not active QPainter::setFont: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::restore: Unbalanced save/restore QPainter::translate: Painter not active QPainter::translate: Painter not active QPainter::save: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::pen: Painter not active QPainter::setFont: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::restore: Unbalanced save/restore QPainter::translate: Painter not active QPainter::translate: Painter not active QPainter::save: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::pen: Painter not active QPainter::setFont: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::restore: Unbalanced save/restore QPainter::translate: Painter not active QPainter::translate: Painter not active QPainter::translate: Painter not active QPainter::begin: Widget painting can only begin as a result of a paintEvent QFile::remove: Empty or null file name
Just a question to make sure this can work: do you have the global option in the settings dialog turned on?
My global settings are: Start with last selected view Price precision 4 digits Autosave off Fiscal year 1 April Calculator kcalc Synchronise, list and title bar all on No filters on other than no transactions before start of 2005
What about your settings on schedules? That's where you find the auto-enter option.
The auto-enter button is checked. That was the first thing I checked when I started using 3.97.2 in case the setting had not been transferred over from 1.0.4 but it was and I have not changed it, for example, by unchecking it and re-checking it. My next scheduled transaction is on 19 May. I was thinking of leaving it until then to see if, now the file has been saved by 3.97.2, the problem has disappeared.
Can you post your anonymized file here, so we can check it out?
Created attachment 43485 [details] Original 1.0.4 with greyed out transaction showing
Created attachment 43486 [details] 3.97.2 file after transaction entered manually
On Tuesday 11 May 2010 19:16:39 John Hudson wrote: > https://bugs.kde.org/show_bug.cgi?id=235880 > > > > > > --- Comment #9 from John Hudson <j r hudson virginmedia com> 2010-05-11 > 20:16:37 --- The auto-enter button is checked. That was the first thing I > checked when I started using 3.97.2 in case the setting had not been > transferred over from 1.0.4 but it was and I have not changed it, for > example, by unchecking it and re-checking it. My next scheduled > transaction is on 19 May. > I had this problem, too, initially. But, my belief afterwards was that settings were not carried over from v1.x because they are in .kde, whereas v3/9X settings will be in .kde4. Perhaps I'm wrong though. I think my problem was sorted by the setting in Schedules, 'Check schedules on startup'. > I was thinking of leaving it until then to see if, now the file has been > saved by 3.97.2, the problem has disappeared. > Allan
Indeed, the user settings are not migrated from 1.x. You have to set the individual schedule to auto-enter. And then you have to go to Configure KMyMoney -> Scheduled transactions -> Enable "Check schedules on startup".
That was the problem. As so many settings are migrated, maybe there needs to be a pop-up warning which ones are not. Thanks for your help.