Don't install CmdPal on upgrade if it was explicitly disabled

[inxomnyaa]

Description of the new feature / enhancement

With every update of PT that Command Palette comes back. I don't want it, Run is already working fine. Having the same functionality in 2 apps is utterly useless.

Scenario when this would be used?

Bad PC, low storage, already using PT Run.

Supporting information

No response

[cinnamon-msft]

Does disabling Command Palette inside PT settings work for you? /needinfo

[inxomnyaa]

That doesn't seem to be the case, no

[zadjii-msft]

You know, there's probably a good point here.

I'm guessing that our installer always installs the CmdPal package, but it only starts it if it is enabled.

We shouldn't even be installing the package if it's disabled.

We discussed (offline) earlier that we can't really uninstall it cleanly on a disable (because that will blow away CmdPal's settings, and recreate them on the enable). But at least this way, if someone disables it and uninstalls it, then the next PT update won't bring it back.

[LucasOe]

Personally, I would also have liked to see a confirmation asking me for confirmation, as I was quite surprised to see it being installed as a separate package. As a power user, I like to know about the applications on my computer.

[HaydenHildreth]

Personally, I would also have liked to see a confirmation asking me for confirmation, as I was quite surprised to see it being installed as a separate package. As a power user, I like to know about the applications on my computer.

I was surprised to see that as well.