Won’t showing a switch in a cell in a list (like for activating Bluetooth/WiFi) confuse users because they could think the cell cannot be selected (and so there is no setting page)?
Or maybe, like for Bluetooth, the setting page should be selected when the switch is toggled. And for WiFi/Internet (that has sub-pages), the “>” indicates that the page can be selected (since the page cannot be selected because the switch would then be hidden).
From what I’m seeing are reading sounds pretty straight forward for most users about the toggles.
Any ETA on when the side button issue that some of use are still having will be resolved? Some of use even with manually editing the one file still cannot get the mouse side buttons to behave the way we want them to behave. Would be really nice if Configure Extra Buttons worked. Currently in my situation I got button 1 to map to control, but button 2 will not do the same as in the pas nor will it map to anything else.
@Mixmax, yes. Google encountered this when they developed AOSP 5. Their solution was to prepend a QSplitter equivalent before the toggle. Where no splitter was, no page existed to click through. Where one was, a page existed that the user could access by selecting the entry before the splitter:
Insofar as they’re invocable via kcmshell6 regardless (which appears to be so), this brings plasma-systemsettings’s KCMs closer to parity with control.exe’s .cpls!