[Task] Disable settings (versus hiding)

[Jay-o-Way]

It's best practice to disable settings that aren't available because of a "master" on/off toggle switch. Synchronizing this behavior means changes to:

• Time
• Background
• Accent color
• Mouse pointers
• (Windows) Theme
• Hotkeys

[Armin2208]

I also prefer disabling the battery powered devices section under conditions instead of hiding it, just to "promote" the possible features for mobile devices, if someone has a secondary device.

[Jay-o-Way]

I also prefer disabling the battery powered devices section under conditions instead of hiding it, just to "promote" the possible features for mobile devices, if someone has a secondary device.

That is a different situation. A battery is not a setting that can be turned on and off at will.

If the device has no battery, showing battery-related options would be:

• Confusing: Users might wonder why those settings exist or whether something is broken.
• Cluttered: Unnecessary options dilute the clarity of the UI.
• Misleading: Disabled battery settings imply the feature is temporarily unavailable — not permanently irrelevan

[ChenYiLins]

I found this problem in the development of another PR a week ago. Options are not unadjustable when the function is turned off, and we should not hide them (users will have an unknown fear and think about what will happen when the ToggleSwitch is turned on). If we choose to show these options, it is a good choice to disable them when the function is turned off.

(But due to some things, I have been too busy recently, and this PR is still on hold)