The audio applet does not behave consistently with all the other applets when it comes to opening the related KCM. Whereas Bluetooth, networking, KDE Connect, energy and possibly other widgets open the related KCM entry, the audio applet opens its own settings window, therefore disregarding consistency.
Furthermore, due to bug 433443 and 433444, there is currently no way to easily open the audio settings KCM without using the right-click menu when the widget is placed directly on the panel.
STEPS TO REPRODUCE
1. Click on the settings icon in the applet.
The applet settings open.
The audio KCM opens.
Linux: KDE neon
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.3
Indeed. This requires first removing the applet's own settings window and migrating all of its settings into the KCM so we don't have two types of configuration anymore (applet-specific and global). That's been done for other applets, but still needs to be done for this one. See Bug 440846.
Now that the audio kcm has a single page, it can be brought back to the applet configuration if that was the way we want forward.
I think it's the reverse: we want the KCM to be the source of truth here and for the applet's configure button to open the KCM, which is what we do for all the other applets at this point.
In principle, none of the applet's current options are applet-specific; they're all global options. So the KCM is really the right place for them, and it should just appear in System Settings IMO. I really think applets should only have settings pages that affect just that specific applet instance. They shouldn't expose global settings in there.
(In reply to Nate Graham from comment #3)
> In principle, none of the applet's current options are applet-specific;
> they're all global options. So the KCM is really the right place for them,
> and it should just appear in System Settings IMO.
Got it! I misleadingly though that those settings were applet-specific
Yeah, that's exactly why they shouldn't live in an applet settings window. :)
*** Bug 443939 has been marked as a duplicate of this bug. ***
*** Bug 445452 has been marked as a duplicate of this bug. ***
*** Bug 456246 has been marked as a duplicate of this bug. ***