Page 1 of 1
(5 posts)

Hi, after new update (1.4.0), my graphs shows different numbres than before.Before update the main graph shows balance of all my accounts in time. Which I find useful as it says if I'm saving or spending and also if I'm close to broke or to some line I didn't want to cross.Now it shows cummulated sum of spending each day, which could be pretty boring graph when money didn't flow, and also it only says that on particular day I spend or earn more but in really weird way.I read changelist and I understand performance issues which leads to throwing away older values. But could you somehow use a balance value as a starter for a graph an draw it from there.

Simply put:when omitting older values take a balance for the day you start drawing a graph so the values stays actual.I know that it may be more problematic as you can graph different stuff.Or another idea, for me, I don't care about performace or I can wait for result, so why don't you make it optional (to omit older values as default) somewhere in a settings.

To get anyone in the picture more easily:last four years I was saving for reconsturction of a housethis year I spend a lot for material and work...but when I look at the graph showing me how are my savings it says i'm totally broke, but when I extend that to 5 year period I'm way above zero. That is the problem I see in thins new computing.

Ok I only post the graph part, because when I anonymized the data, the result graph looks different (to be precise it looks like waterslide).this is the graph for 3 year long time interval (from 3 years back to now)

this is the graph for 1 year long time interval (from 1 year back to now)

Problem for me is in the second one it looks like I'm mostly in red numbers, while looking in a 3 year long time period there are just few moments I was in red.What I want, is to view just 1 year back, but with the real amounts on that accounts.

Hmm, if I understood correctly, looks like the "one year" graph starts at 0€, without taking into account the values from before... Definitely a bug. Can you please open a report on http://bugs.kde.org, please ?