5.1.3 is better than 5.2.1

[Philippe Debrabant]

Hi Jack and Thomas,

Thank you for your answers. I'm a very long time user of KMyMoney and I 
like very much the software.

I don't understand why this application is not updated regularly in my 
distro (LMDE), but it's another question...

I understand that your future work concerns the 5.2 version only and I 
hope that the side effects of the important updates will be corrected 
soon. I'll be glad to help you to debug some incidents. Do you have any 
tutorial or procedure to configure the development environment on a 
Linux workstation ?

I will tried the AppImage to see if the behavior is different than the 
flatpak package, but I agree with you Thomas, I don't think that I will 
see any difference in speed.

My best regards,

Philippe

Le 02/11/2025 à 11:41, Thomas Baumgart via KMyMoney a écrit :
> Please see my comments inline below.
>
> On Samstag, 1. November 2025 19:18:05 CET Jack via KMyMoney wrote:
>
>> On 2025.10.31 09:50, Philippe Debrabant via KMyMoney wrote:
>>> Hi all,
>>>
>>> I also reverted to version 5.1.3 after testing 5.2.1 (Flatpak
>>> package).
>>>
>>> 5.1.3 is:
>>>
>>> - much, much faster
>>> - much more responsive: I reconciled an account with 5.2.1, and after
>>> pressing the "finish" button, the process took almost a minute,
>>> whereas with 5.1.3 it's instantaneous.
>>> - I searched for a transaction by typing a keyword; a list appeared,
>>> but it was impossible to view the transaction description, and
>>> double-clicking on a transaction didn't open it in the Ledger.
>>>
>>> And what about the usability:
>>>
>>> - The placement of the button for a new transaction at the top of the
>>> screen is poorly chosen. The previous location is preferable.
>>> - The dialog box for entering a transaction is too complex; entering
>>> a transaction takes longer.
>>>
>>> In short, I'm going back to the previous version until something
>>> better comes along.
>>>
>>> After waiting so long for improvements, I must admit I'm very
>>> disappointed with the result.
>>>
>>> Philippe
>> Philippe,
>>
>> In terms of speed, although I don't know exactly how much it matters, I
>> assume you are comparing a natively compiled application (5.1.3) to a
>> containerized on (5.2.1 Flatpak.)  You might try the Appimage to see if
>> it is any faster than the Flatpak.
> I have never played with Flatpaks, but I would be astonished if it makes
> a big difference in speed.
>
>> In addition, at least some of that speed difference is due to the new
>> version doing more behind the scenes, in terms of confirming validity
>> of the data (especially during imports.)  I agree that the finish part
>> of a reconciliation is slower than previously, but I don't find the
>> difference that much.
> Triggered by Philippe's report I spent some time and investigated load times
> again. I noticed a bottleneck that shows even more, the more accounts you
> have that are not assigned to an institution. Fortunately, that was easy
> to fix.
>
>> When you talk about your problem searching for a transaction, is this
>> in the search/status field you get by typing Ctl-F, or using the
>> Transaction Search dialog?  You said you got a list, but in the former,
>> the ledger is simply filtered to show transactions which match the
>> search, so the information displayed about each transaction is whatever
>> is normally shown in the ledger.
> It looks like another Qt6 based problem. I was able to duplicate it using
> a Qt6 version. On Qt5 it works as expected.
>
>> In the latter, I am not aware that
>> result list is any different in 5.2.1 compared to 5.1.3,  For me, I do
>> see the full details of each transaction, and double clicking does take
>> me to the transaction in the ledger.  I do not know if any of your
>> issues are related to using the Flatpak version, which I have not yet
>> tried.
>>
>> I'm not sure which button you mean regarding entering a new
>> transaction, but Ctl-Ins or clicking in the bottom row of the ledger
>> both seem reasonably fast and accessible to me.
>>
>> You are obviously welcome to continue using 5.1.3, but understand, it
>> is no longer supported, meaning that even if you do find a real bug,
>> which is not already fixed in a newer version, it will only be fixed in
>> 5.2.something.
>>
>> Hopefully you will be happier either with an Appimage or a disto
>> packaged version (I know this depends on your distro.)
>>
>> Jack