Invert opacity setting

[Katsute]

Relevant Issues

List any closed and/or relevant issues

• Closes Invert opacity setting #370

Changes Made

List any changes made.

• Invert opacity calculation
• Add option to use old behavior

Release Notes

Going forward, to achieve parity with other background extensions, the opacity calculation will be switched from 0 visible and 1 invisible to 1 visible and 0 invisible.

To use the old behavior, use the useInvertedOpacity option. If you already have an opacity set, the inverted opacity setting will automatically be turned on.

[Katsute]

Use globalState to keep track if the migration process ran.

Use a key like migratedOpacity instead of a generic one as we may want to do more migrations in the future.

Migration logic must exist permanently so users that don't update for a long period still keep their settings.

On first launch:

• If migrate has not ran:

  • If opacity value exists, turn the inverse opacity flag on
  • If opacity doesn't exist do nothing

  set migrate to true in globalState to indicate this already ran

• If migrate has run:

  • Do nothing (do not re-migrate)

[Katsute]

Setting logic from #383 needs to be merged first so we can use it to check if opacity setting is set instead of falling back to the default

[Katsute]

On update, VS complains that the manifest doesn't contain the new option, all while it IS using the updated code

Need to test with install/uninstall then new ver

[Katsute]

✅ Install/Uninstall + VSIX Load passed

[Katsute]

show notification on migrate

show notification on missing option (vscode bug) - prompt to reload

[kdevbot]

Approved by @Katsute