[frameworks-kconfigwidgets] [Bug 373764] `KColorScheme::adjustBackground` and other methods ignore effects of `KColorSchemeManager::activateScheme`

[Francis Herne]

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

Francis Herne <m...@flherne.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|regression                  |
          Component|UI: general                 |general
           Assignee|kdevelop-bugs-n...@kde.org  |kdelibs-b...@kde.org
            Product|kdevelop                    |frameworks-kconfigwidgets
            Summary|"Find:" contents unreadable |`KColorScheme::adjustBackgr
                   |in dark themes              |ound` and other methods
                   |                            |ignore effects of
                   |                            |`KColorSchemeManager::activ
                   |                            |ateScheme`
            Version|git master                  |5.29.0
   Target Milestone|5.1.0                       |---
           Priority|LO                          |NOR

--- Comment #4 from Francis Herne <m...@flherne.uk> ---
So, passing
`KSharedConfig::openConfig(qApp->property("KDE_COLOR_SCHEME_PATH").toString()`
into all the KColorScheme::foo() calls makes this work.

There are actually less-obvious effects from other uses of KColorScheme, e.g.
in the CMake status text colour.

I'm pretty sure this should be handled in KColorScheme - after all, the
property is set by KColorSchemeManager, and KTextEditor shouldn't need to care
whether a parent application is using that.


[moving bug]

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