Skip to content

Conversation

@SeraphimaZykova
Copy link
Contributor

Summary of the Pull Request

What is this about:

I decided to split the fix into separate issues for each part of the zones-settings. This is the first part with layout hotkeys.

  • Keep layout hotkeys in a separate file.
  • Removed layout hotkeys from FancyZonesData
  • Replace old zones-settings on FZ start
  • Unit tests

What is included in the PR:

How does someone test / validate:

Quality Checklist

Contributor License Agreement (CLA)

A CLA must be signed. If not, go over here and sign the CLA.

@github-actions

This comment has been minimized.

Copy link
Contributor

@stefansjfw stefansjfw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added few minor comments, but overall looks good and works good!


void FancyZonesData::ReplaceZoneSettingsFileFromOlderVersions()
{
if (std::filesystem::exists(zonesSettingsFileName))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

once it's migrated, no need to do it every time? add && if NOT exist hotkeysFile to condition?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm planning to add the code removing the zones-settings.json after I finish with other parts. So checking only this one will be enough.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok. that makes sense

@SeraphimaZykova SeraphimaZykova merged commit ba431c5 into microsoft:main Jan 17, 2022
@SeraphimaZykova SeraphimaZykova deleted the 14782-fancyzones-forgets-custom-layouts branch January 17, 2022 08:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants