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

cwo <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
            Version|                            |KF 6.27
  Fixed/Implemented|                            |
                 In|                            |
         Resolution|---                         |FIXED
      Latest Commit|                            |https://invent.kde.org/fram
                   |                            |eworks/kiconthemes/-/commit
                   |                            |/c095f89c9b8b42f64a99110223
                   |                            |853d3d25c68d4f

--- Comment #4 from cwo <[email protected]> ---
Git commit c095f89c9b8b42f64a99110223853d3d25c68d4f by Christoph Wolk.
Committed on 11/05/2026 at 08:36.
Pushed by cwo into branch 'master'.

widgets/kicondialog: clear custom when pressing OK

KIconDialog stores the custom path in the Private class member custom;
slotOk always prefers the custom member (if set) over the currently
selected item in the grid. Double-clicking an icon from the grid clears
custom first before calling slotOk, but pressing the OK button does not.
This means that if the dialog is reused and the user first accepts an
icon through file system browsing, then reopens the dialog and tries to
choose an icon from the grid by selecting it and pressing OK, the icon
will remain stuck on the original (browsed) icon. But if the user
double-clicks the icon there instead, everything works out fine.

So we also clear the custom member when pressing OK, not just when
double-clicking. To avoid code duplication, we give the existing lambda
a local name and reuse it.
FIXED-IN: KF 6.27

M  +5    -3    src/widgets/kicondialog.cpp

https://invent.kde.org/frameworks/kiconthemes/-/commit/c095f89c9b8b42f64a99110223853d3d25c68d4f

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

Reply via email to