Bug 369635 - Allow to change UI colors, not just editor theme
Summary: Allow to change UI colors, not just editor theme
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: UI: general (show other bugs)
Version: 5.0.1
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-02 12:16 UTC by Janek Bevendorff
Modified: 2016-10-08 14:04 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In: 5.1.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Janek Bevendorff 2016-10-02 12:16:20 UTC
I reported this already as bug #369633 for Kate, but since only the editor component is shared, but not the actual UI, I thought I might file this feature request for KDevelop again. Please close it if you think it's redundant.

KDevelop now has a Breeze Dark theme which is provided by the Kate editor component. However, the overall UI still has the global desktop theme. It would be great if KDevelop allowed me to change the UI theme independent of my global desktop settings (like Krita does). I generally prefer the bright Breeze theme, but I can't work with an editor for hours that has such a bright theme. Using a dark editor theme with a bright UI results in really high contrast and doesn't go much easier on the eye than an overall bright editor theme.

Reproducible: Always
Comment 1 Christoph Feck 2016-10-07 02:07:09 UTC
According to http://commits.kde.org/kdevelop/f6965687228383239cdf5b1e97c012e82fd5d119 there should already be a settings menu to select the color scheme.
Comment 2 Janek Bevendorff 2016-10-08 10:15:29 UTC
Looking at the diff, this should be in the settings menu. But there is
no such entry, at least not in the current stable version (5.0.1). Maybe
it didn't make it into the release?
Comment 3 Kevin Funk 2016-10-08 14:04:19 UTC
@Janek: This went into master branch only which represents the unreleased 5.1 branch at this point. So this will be fixed for 5.1.0 release.