search

microsoft / PowerToys

Windows system utilities to maximize productivity
MIT License
111.68k stars 6.57k forks source link

Global enable/disable of File Explorer add-ons #16039

Open k3davis opened 2 years ago

k3davis commented 2 years ago

Description of the new feature / enhancement

Other powertoys have a master toggle to enable or disable them, but File Explorer add-ons does not. This is less than desirable especially since new items that are added are automatically enabled by default.

I would like there to be a master toggle for all the add-ons like the other powertoys, or at least an option not to enable newly added functions by default.

Scenario when this would be used?

When you don't want to have features automatically enabled when new File Explorer functions are added, especially those that need a restart to disable after the fact.

Supporting information

No response

scscgit commented 2 years ago

"option not to enable newly added functions by default."

-> Could we also generalize this requirement a bit more, providing a new global configuration to select a default behavior of config for any new/changed add-ons, while also turning this into a promise that any future development will have to adhere to (rather than having undefined behavior, which as developers you "surely" love)?

Most importantly, this is one of the reasons why using auto-updates is insane with apps like this, as devs can never avoid adding breaking changes, and there's no way to satisfy everyone by making choices for them. We need at least a guarantee (an option) of any new configuration being disabled by default. However, even if we do the updates manually, it's likely that we may want to enable some new features (especially if developers assume that everyone wants them by default), so my suggestion would be to also keep track of configuration that wasn't explicitly disabled, and to display any such diff near the Update section. Majority of the users may still prefer to keep the new defaults, but for those of us who've consciously chosen to agree with each default individually, it's vital that nothing new gets added before we approve it, otherwise the auto-update is pointless (and we can't reasonably go through each changelog if we've skipped too many versions and need to update without any breaking changes).