Severe bug in reports in master branch

[Cristian Oneț]

Hi Łukasz,

Indeed the report transaction order bug has been fixed.

The budget related crash is still there.

I also have to say that after another update that I ran today, the
forecast feature seems to have stopped working "as before", it is
getting harder and harder to keep up with the changes as a user.

2017-06-21 13:49 GMT+03:00 Łukasz Wojniłowicz <lukasz.wojnilowicz at gmail.com>:
> Hi Cristian,
>
> Please test latest master branch because I think your issues are fixed.
>
> Referring to order of transactions in report after transaction modification, it
> was sorting, that was to blame.
> I changed it intentionally while implementing multicurrency totals, but it
> broke your use case, so I returned old sorting.
> First tests show that my use case isn't broken and yours work too, but I would
> expect troubles with multicurrency totals anyways somewhere in future.
>
> During the research, I found a bug (not critical) that transaction IDs written
> to .kmy file aren't being red from the file. Transaction IDs are assigned
> through function during KMM start and stay so till application quits.
> The assignment is according to date. When one changes date, the assigned ID
> won't change till KMM starts anew. The assigned ID is being written to .kmy
> file, but won't be red, because KMM will assign new IDs at start.
> That was the reason why your reports showed correctly after restart.
>
> Cheers
>
> Łukasz