Bug 411317 - Editing active color scheme doesn't immediately apply changes
Summary: Editing active color scheme doesn't immediately apply changes
Status: CONFIRMED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_colors (show other bugs)
Version: 5.16.4
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: Matthew Woehlke
URL:
Keywords: usability
: 441833 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-08-26 12:28 UTC by Michael D
Modified: 2021-09-02 06:03 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
KColorSchemeEditor window (122.34 KB, image/png)
2019-08-26 18:20 UTC, Michael D
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael D 2019-08-26 12:28:10 UTC
If I have custom color scheme X active and edit it by changing e.g. the active titlebar color, nothing happens when I click apply. I have to select another theme, apply it, and then reapply X in order to get the chances to take effect.
Comment 1 Nate Graham 2019-08-26 16:44:43 UTC
Can confirm. This is because when the edited color scheme is the active one, the color editor has no "Save" or "Apply" button, and does not auto-apply any changes made when it's closed.
Comment 2 Michael D 2019-08-26 17:16:06 UTC
There *is* an "Apply" button for *custom* color themes, but it doesn't work.
Comment 3 Nate Graham 2019-08-26 18:06:31 UTC
I mean, there's no Save or Apply button in the editor window itself.
Comment 4 Michael D 2019-08-26 18:19:52 UTC
Unless I'm confused, it was always like this, but changes were immediately applied after clicking "Apply" within the kcolorscheme editor window, as in the screenshot attached.
Comment 5 Michael D 2019-08-26 18:20:31 UTC
Created attachment 122376 [details]
KColorSchemeEditor window
Comment 6 Nate Graham 2019-08-26 18:21:56 UTC
That's odd, mine doesn't have the Apply button for any color schemes (built-in, custom, or otherwise).
Comment 7 Michael D 2019-08-26 18:26:36 UTC
Maybe because I had created a custom scheme long ago it affected the presence of the "Apply" button?
Comment 8 Nate Graham 2021-09-01 16:01:24 UTC
*** Bug 441833 has been marked as a duplicate of this bug. ***
Comment 9 Nate Graham 2021-09-01 16:24:10 UTC
I see the issue. the "Apply" button in the editor window basically acts like a "Save" button. Once you click it, the state is marked as dirty, so you need to close the window and click the "Apply" button in the main KCM window to actually really truly apply the changes.
Comment 10 Nate Graham 2021-09-01 16:49:31 UTC
To make the Apply button (which I am changing to "Save" in https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1034) instantly apply the changes, we need a way for the dialog to communicate with the base KCM. They are in fact separate apps. Right now their only source of communication is that the KCM reads the exit status of the editor app when its window is closed. Probably we would need for the KCM to expose a DBus "Apply right now" method, and then the editor window would call it when clicking the "Save" button.

I might look into this if I'm ever in a masochistic mood, as doing anything with DBus always ruins the rest of my day.

Overall, this is screaming out for the editor to be integrated into the KCM itself as a sub-page, rather than a separate windowed app.
Comment 11 Nate Graham 2021-09-01 22:33:26 UTC
Git commit f4ad2fb1ce9d718c7506bc30fc5d20971de27d14 by Nate Graham.
Committed on 01/09/2021 at 22:33.
Pushed by ngraham into branch 'master'.

kcms/colors: change "Apply" button to "Save"

It's a bit odd to have a "Save As..." Button but no "Save" button. The
"Apply" Button does the same thing that a save button would, and is
active during the same times, so let's just make it *be* a "Save"
button.

M  +2    -1    kcms/colors/editor/scmeditordialog.cpp

https://invent.kde.org/plasma/plasma-workspace/commit/f4ad2fb1ce9d718c7506bc30fc5d20971de27d14
Comment 12 Michael D 2021-09-02 06:03:04 UTC
Great, thanks!