Ledger Behavior

[Brendan Coupe]

On 1/27/26 8:05 AM, Jack via KMyMoney-devel wrote:
> On 1/27/26 5:27 AM, Paul Worrall via KMyMoney-devel wrote:
>> On Monday, 26 January 2026 20:00:44 Greenwich Mean Time Jack via 
>> KMyMoney-
>> devel wrote:
>>> On 1/26/26 2:09 PM, Brendan Coupe via KMyMoney-devel wrote:
>>>> I'm running the latest master compiled on Fedora 43 yesterday.
>>>>
>>>> I'm posting a question here rather than submitting a bug report since
>>>> I'm not sure how to search for a similar bug since someone else may
>>>> use different terms to describe it and I don't want to file a
>>>> duplicate bug report. If it is needed, I will file a bug report.
>>>>
>>>> At certain times, the ledger scrolls up making me scroll back down to
>>>> the bottom of the ledger to see my most recent transactions.
>>>>
>>>> The easiest way to experience the bug is to scroll to the bottom of
>>>> the ledger, right click on the most recent transaction and select
>>>> "duplicate". When I do this, it always moves up in the ledger so that
>>>> I can not see the new transaction that was added or the most recent 5
>>>> or 10 transactions. I have to scroll down many transactions to get to
>>>> the bottom of the ledger. This also happens when I import a CSV file.
>>>> If I scroll down to the bottom of the ledger and then import the CSV
>>>> file, the ledger scrolls up so I can't see the imported transactions
>>>> or the most recent 5 or 10 transactions that were showing before the
>>>> import.
>>>>
>>>> While testing this on several accounts, I realized this seems to
>>>> affect every account ledger when I access them. They are never at the
>>>> bottom of the ledger and I have to scroll down to the bottom each 
>>>> time.
>>>>
>>>> I do not think this is how KMM 5.1 behaved but it has been a long time
>>>> since I have used 5.1.
>>> I do think this has been mentioned before, but not sure if bug,
>>> discuss.kde.org, or mailing list.  Search term to add might be
>>> scrolling.  One difference is that what I have noticed is that 
>>> afterThis is about the ledger scrolling to the "wrong" place after 
>>> completing
>>> an action, rather than multiple redraws during an action., so it's not
>>> quite the same thing, although it's certainly possible that commit also
>>> fixes this problem.
>>>
>>> doing something to a transaction (typically the newest or close to it)
>>> when you Accept, the ledger scrolls to the top/oldest.  For now, no 
>>> need
>>> for a bug, unless we can get a more consistent behavior.  In any 
>>> case, I
>>> suspect it would have to do with how the  focus gets set after 
>>> accepting
>>> the previous actions.
>>>
>>> Jack
>> This seems similar to bug 514417 
>> <https://bugs.kde.org/show_bug.cgi?id=514417>
>> which applies to reconcile mode and which has been fixed by a recent 
>> commit.
> This is about the ledger scrolling to the "wrong" place after 
> completing an action, rather than multiple redraws during an action, 
> so it's not quite the same thing, although it's certainly possible 
> that commit also fixes this problem.

I just recompiled KMM and the problem is not gone so if the mentioned 
bug has been fixed, this is not related.

Has anyone tried to duplicate the problem? I just opened a ledger and I 
was not at the bottom of the ledger (therefore this is not just after 
taking an action in the ledger but also when entering the ledger 
initially). This happens on every account ledger I have tried it on.

I scrolled to the bottom and duplicated the most recent transaction. The 
ledger scrolled up many transactions so that I had to scroll back down 
to the bottom to see the new transaction.

When opening the ledger it scrolls up so that transactions in September 
are at the bottom. There are probably 40 to 50 newer transactions below 
it. After duplicating the most recent transaction it scrolls back up so 
that the bottom transaction is also in September but down 1 or 2 from 
the previous one that was at the bottom when I opened the ledger.

It seems like this is not some random action but something that is being 
triggered by something in the code (I assume unintentionally).

-- 
Brendan