https://bugs.kde.org/show_bug.cgi?id=517297

            Bug ID: 517297
           Summary: Entering the "Scheduled Transactions" screen alters
                    the "Alt+" shortcut for "New Book/Transaction/etc."
    Classification: Applications
           Product: kmymoney
      Version First 5.2.2
       Reported In:
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: ux-ui
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

SUMMARY

NOTE: This may only affect en_US localizations, (or the shortcuts may be
different). I can only speak for en_US.

Entering the "Scheduled Transactions" alters the "Alt+" shortcut used on most
screens for a "New" action ("New transaction", "New category", etc"). This is
by default set to "n", allowing you to use "Alt-n" to enter a new transaction.
But when you select "Scheduled transactions" from the left navbar, this
shortcut changes to "w" for some reason. This change appears to be
irreversible, and the shortcut will remain broken until you quit the
application and start it again.

STEPS TO REPRODUCE
1. Open KMyMoney. Observe the underline under the "N", marking "n" as the
"Alt+" shortcut for this button.
2. Enter a ledger and note that pressing "Alt+n" will allow you to enter a new
transaction. Click Cancel (or press Esc) to cancel entering the transaction.
3. Click "Scheduled transactions" on the left navbar.

OBSERVED RESULT

The "New schedule" button shows an underline under the "w" now. If you return
to a ledger, the "New transaction" button still shows the underline under "w".
"Alt-n" is now the shortcut for "Find transaction", while you need to use
"Alt-w" to enter a new transaction.

EXPECTED RESULT

Keyboard shortcuts should remain consistent.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: kernel version 6.19.6-arch1-1
KDE Plasma Version: 6.6.2
KDE Frameworks Version: 6.23.0 
Qt Version: 6.10.2

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to