[Kmymoney-devel] [Bug 283858] KMyMoney v4.6.0 (Windows) Help error "requested help file could not be parsed".

https://bugs.kde.org/show_bug.cgi?id=283858 --- Comment #18 from Steffie 2012-01-28 03:37:39 --- Hello. Re "There is recently 4.8.0 available", now i went to http://windows.kde.org/download.php , downloaded the latest KDE-Installer for Win [seems to be v0.9.9-5], selected the Package Manage

Re: [Kmymoney-devel] astyle problems continue

On 27/01/12 20:15, Thomas Baumgart wrote: Hi, on Friday 27 January 2012 15:08:00 Allan wrote: On 27/01/12 13:54, Allan wrote: On 27/01/12 11:55, Allan wrote: Be aware that there is a second step that is run after the astyle command did its thing. The comment in astyle.sh says: # process the

Re: [Kmymoney-devel] astyle problems continue

Hi, on Friday 27 January 2012 15:08:00 Allan wrote: > On 27/01/12 13:54, Allan wrote: > > On 27/01/12 11:55, Allan wrote: > Be aware that there is a second step that is run after the astyle > command did > its thing. The comment in astyle.sh says: > > # process the same

[Kmymoney-devel] [Bug 283858] KMyMoney v4.6.0 (Windows) Help error "requested help file could not be parsed".

https://bugs.kde.org/show_bug.cgi?id=283858 --- Comment #17 from Ralf Habacker 2012-01-27 14:35:24 --- (In reply to comment #15) > Hi Ralf. You said "Now the people working on the 4.7.4 release need to be > informed that an updated binary kdelibs package is required" ... does this > next >

Re: [Kmymoney-devel] astyle problems continue

On 27/01/12 13:54, Allan wrote: On 27/01/12 11:55, Allan wrote: Be aware that there is a second step that is run after the astyle command did its thing. The comment in astyle.sh says: # process the same set of files to replace "foreach(" with "foreach (" which is exactly what is done. Now if

[Kmymoney-devel] astyle problems continue

On 27/01/12 11:55, Allan wrote: Be aware that there is a second step that is run after the astyle command did its thing. The comment in astyle.sh says: # process the same set of files to replace "foreach(" with "foreach (" which is exactly what is done. Now if you run the script again, astyle

[Kmymoney-devel] [Bug 283858] KMyMoney v4.6.0 (Windows) Help error "requested help file could not be parsed".

https://bugs.kde.org/show_bug.cgi?id=283858 --- Comment #16 from Sebastian Trueg 2012-01-27 13:20:48 --- Git commit 45e453002a1e07eb13747e0f21342be01c838ddc by Sebastian Trueg, on behalf of Ralf Habacker. Committed on 30/12/2011 at 23:19. Pushed by trueg into branch 'KDE/4.8'. crash fix on

Re: [Kmymoney-devel] Bug: SQLite storing Bi-weekly as weekly?

On Tue, 24 Jan 2012 16:54:32 -0500 Eric Bonney wrote: > In working on my project this afternoon I think I may see a bug? > Looking at my raw sqlite data I have schedules that have an > occurenceString of Every Other Week, but the occurrence column shows > 4. > > Now looking at the mymonyschedule.

Re: [Kmymoney-devel] Review Request: Add profiles to csvplugin to retain user's settings

Be aware that there is a second step that is run after the astyle command did its thing. The comment in astyle.sh says: # process the same set of files to replace "foreach(" with "foreach (" which is exactly what is done. Now if you run the script again, astyle changes "foreach (" into "foreach

Re: [Kmymoney-devel] KMyMoney 4.6.2 release schedule notification

Having just seen this - ">> 2. Is this a bugfix? (question towards the other devs) Sort of, I think. Then it will make it in the upcoming 4.6.2" I have a question. There is a long-standing bug I submitted about the missing QIF investment export feature. I do now have this working, but was

Re: [Kmymoney-devel] Review Request: Add profiles to csvplugin to retain user's settings

On 27/01/12 06:08, Thomas Baumgart wrote: Hi, on Friday 27 January 2012 01:01:43 Allan Anderson wrote: On Jan. 26, 2012, 6:16 p.m., Cristian Oneț wrote: kmymoney/plugins/csvimport/convdate.cpp, line 47 What ha

Re: [Kmymoney-devel] Review Request: Add profiles to csvplugin to retain user's settings

> On Jan. 26, 2012, 6:17 p.m., Cristian Oneț wrote: > > Please revert all whitespace changes to their previous state which was in > > according to our coding style. Another reason to do that is that all those > > changes pollute the patch and make it hard to follow. > > Until then I'll test it