[docs] tracker for 0.35 updates

[enricogior]

@dedavis6797
I'm going to use this issue to list the changes for 0.35

• FancyZones quick layout switch [FanzyZone][FZ Editor] Layout hotkeys / quick swap #1411
  it brings new UI in the FZ Editor for custom layouts only (not for templates)
  see the UI here [FZ Editor] Layout hotkeys label should fit the dialog. #10310
  NOTE: we still have to make the final call on the actual shortcut

[htcfreek]

@enricogior

Please add

• PT Run Monitor settings ([Run] "launch on monitor" setting for multimonitor user #1607)
• VS Code Plugin ([Run][New Plugin] VSCode opened workspaces plugin #3547)

---

Let's add the tracker label.

[dedavis6797]

Current draft PR for the docs: MicrosoftDocs/windows-dev-docs#3023

[htcfreek]

@dedavis6797
Looked at the draft docs. The description of PT Run's monitor settings is incorrect. We implement it in an other way as original planned.

Will post an updated image later.

[htcfreek]

@dedavis6797
Looked at the draft docs. The description of PT Run's monitor settings is incorrect. We implement it in an other way as original planned.

Will post an updated image later.

@dedavis6797
Here you go. The selected option is the default settings after a fresh install on a new system.

[enricogior]

@dedavis6797
we need to update the image in the Space around zones section since it's outdated
https://docs.microsoft.com/en-us/windows/powertoys/fancyzones#space-around-zones

to the current UI:

Given the dialog is the same that is used for the new layout quick apply feature, we may consider merging the two sections.

Regarding:

As of PowerToys v0.35, once a custom layout has been created, the layout can use a user-defined hotkey to quickly apply it to the desired desktop. The hotkey can be set by opening the custom layout's edit menu.

I would suggest we don't put the version number, otherwise other time it's going to be quite confusing to have multiple versions referenced.

[enricogior]

@dedavis6797
for the quick layout switch, we managed to provide also a second way of doing it:

• start dragging a window and then press the number key (no modifier are necessary)
  it doesn't require the zones to be visible, so it can be done without having to press Shift, but it can be done while pressing Shift.
  At the moment we don't document that in the Editor, but we should document it in the docs.
  In 0.37 we will consider adding the information in the editor as well.

[htcfreek]

@enricogior
This docs tracker issue is a great idea. 👍👍👍👍 We should do this for every release. And maybe as pinned issue.

[dedavis6797]

@enricogior yep, I noticed that when I was playing around with it earlier (awesome feature btw). I have updates to reflect this on my local branch of the Docs, but I haven't committed it yet because I'm still preparing a GIF demonstration of the experience. Should be updated in a few hours.

@htcfreek agreed 👍🏾. We just need to make sure these Docs trackers (and the actual Docs PR's themselves) get enough visibility from the PowerToys community for feedback.

[htcfreek]

@enricogior
Please pin this issue and the tracker issues (docs, workitems) for 0.37. Thank you.

[dedavis6797]

Just updated the Docs PR, if anyone has any other feedback before we have our editors review, please let me know!

[htcfreek]

@dedavis6797

• I requested a change in pr directly.
• In Run page we have version numbers left over. (Paragraph "commandline parameter for apps".
• Missing docs/mention of "vs code" plugin. (Comment update 1)

[dedavis6797]

Thanks for those call-outs @htcfreek, I updated the PR to reflect them.

• Missing docs/mention of "vs code" plugin. (Comment update 1)

I'm not sure what you mean by this. We explain the vscode plugin functionality in the Action Key section. Are you suggesting we explicitly call out that this is a plugin in its own, independent section?

[htcfreek]

@dedavis6797

• Missing docs/mention of "vs code" plugin. (Comment update 1)

I'm not sure what you mean by this. We explain the vscode plugin functionality in the Action Key section. Are you suggesting we explicitly call out that this is a plugin in its own, independent section?

Sory. My mistake.