Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FancyZones] - Editor v2 #1032

Closed
6 of 16 tasks
crutkas opened this issue Dec 31, 2019 · 60 comments
Closed
6 of 16 tasks

[FancyZones] - Editor v2 #1032

crutkas opened this issue Dec 31, 2019 · 60 comments
Assignees
Labels
Area-Quality Stability, Performance, Etc. FancyZones-Editor Issue revolving the FancyZone Editor FancyZones-Layouts Issue for layouts in FancyZones Needs-Spec Something needs additional thought on how we'll implement Tracker Issue that is used to collect multiple sub-issues about a feature

Comments

@crutkas
Copy link
Member

crutkas commented Dec 31, 2019

FancyZone Editor v2

Current list of like-to-have improvements

Things to think about:

  • Possibly think about 'magnetic / dock sides'
  • Percentages versus hard numbers. This will allow me to move a custom layout instantly to a different resolution monitor
  • how a zone can cross monitor boundaries

FAR from done / perfect but doing a first stab at a spec.

https://github.com/microsoft/PowerToys/blob/dev/crutkas/FzEditor2Spec/doc/specs/FancyZoneEditorV2.md

@crutkas crutkas added the FancyZones-Editor Issue revolving the FancyZone Editor label Dec 31, 2019
@crutkas crutkas added this to the Backlog milestone Dec 31, 2019
@DavidGretzschel
Copy link

Another vote for for the importance of Zone-Numbering.

Before I could only come up with rather implausible theoretical situations, why it's needed, but now I actually stumbled over it in actual use:
Here's a reencatment of the scenario:
https://www.youtube.com/watch?v=R5hBqY5GZz4&feature=youtu.be

Also notice that there was a very clear user expectation (well my own, but I think it was plausible) that directly contradicted with the "hidden numbers".
So instead of only showing me what Zones 1, 2, 3 are, I think there should also be the option of telling the editor what 1,2, and 3 are.
Right-clicking into a Zone is currently treated the same as a left-click (which is frankly irritating, since a Windows-user naturally expects more options when right-clicking).
If I click somewhere into Zone 1, it could instead show a variable-size context menu that says:
swap with Zone 2
swap with Zone 3
...
swap with Zone n

And having a right-click menu for a Zone is also a good home for Zone-specific functionality, that hasn't been thought of yet. Or for Layout-specific settings, too.

@hawkerm
Copy link

hawkerm commented Jan 30, 2020

It'd be nice if the zones could display their coordinates and size in the editor. Also, it'd be great if there was a way to snap a zone to a specific size easily like 1920x1080.

@crutkas
Copy link
Member Author

crutkas commented Jan 31, 2020

it'd be great if there was a way to snap a zone to a specific size easily like 1920x1080.

@hawkerm As in presets or would just having txt fields be enough where you could input the numbers

@hawkerm
Copy link

hawkerm commented Jan 31, 2020

@crutkas input fields minimum, presets nice to have.

@crutkas crutkas self-assigned this Feb 5, 2020
@crutkas crutkas added the Needs-Spec Something needs additional thought on how we'll implement label Feb 5, 2020
@crutkas crutkas modified the milestones: Backlog, v1.0 Release Feb 12, 2020
@SCWells72
Copy link

I've been using DisplayFusion's monitor splitter for a long while. So far I really like what I see in FancyZones, and it seems quite a bit faster overall than DisplayFusion, but I am missing some of the features from DisplayFusion in terms of both configuration and runtime behavior:

  • Explicit configuration of zone dimensions - I'd like to be able to click on a zone and say that it should be (0, 0) - (1719, 1439), add another that's (1720, 0) - (2579, 719), etc. That would allow me to VERY carefully configure my zones so that they're non-overlapping and each takes up the exact proportion of the screen that I prefer for the app(s) that I'll place there.
  • Explicit numbering of zones - Others have already mentioned this, but it's very useful when combined with Win+Left/Right for a sort of "tab ordering" behavior when moving windows, both within a screen's zones and across multiple screens' zones.
  • Snapping to zones when dragging windows - In DisplayFusion when I start dragging a window, the various zones highlight. If I drop a window, it snaps to the highlighted zone for both size and position. I can hold a modifier key to suppress this behavior and allow arbitrary drag-and-drop movement of windows as well.
  • (Stretch goal) Zones for the task bar - This is another thing that DisplayFusion allows. I have two UWHD screens, so having the task bar extend across the full width isn't very helpful. In DisplayFusion I can designate zones that should have the task bar and those that shouldn't. I only add the task bar to the two "innermost" zones of the side-by-side screens.

Anyway, just adding to the wish list that's developing here...what you guys have done so far is pretty fantastic! Keep up the great work!

@crutkas
Copy link
Member Author

crutkas commented Feb 26, 2020

FAR from done / perfect but doing a first stab at a spec.

https://github.com/microsoft/PowerToys/blob/dev/crutkas/FzEditor2Spec/doc/specs/FancyZoneEditorV2.md

@crutkas
Copy link
Member Author

crutkas commented Feb 26, 2020

@SCWells72

  • Could do magnet snapping to solve the overlapping issue.
  • called out in the rough spec
  • don't we do that already w/ shift key?

@SCWells72
Copy link

@crutkas I didn't realize that shift+drag would constrain to defined zones. That's great! I guess I need to pay better attention to the documentation.

@crutkas
Copy link
Member Author

crutkas commented Feb 26, 2020

We need better OOBE :)

@enricogior
Copy link
Contributor

I found inconsistent that there is an icon to delete a custom template (one click) and a general button to edit a selected template that requires to click in two places that can be very apart from each other. Let's just get rid of the Edit selected layout and add an edit icon beside the delete icon. Also the delete command doesn't prompt for confirmation and it doesn't have an undo option, we need at least one of them, better to have both.
Using the same logic, it would be nice to remove the Apply button as well, and allow to apply a template with just one click.

image

@enricogior
Copy link
Contributor

When adding new zones in a custom template, the new zone should be of the same size of the last added zone.

@crutkas
Copy link
Member Author

crutkas commented Feb 29, 2020

Yes times 1000 for both edit, delete, apply

Using the same logic, it would be nice to remove the Apply button as well, and allow to apply a template with just one click.

@enricogior
Copy link
Contributor

Linking user's feedback on current limitations/problems when creating layouts for multiple monitors
#941 (comment)

@htcfreek
Copy link
Collaborator

I think we should add a Bug reporting window like in PT Run to the new editor. Then the user can better check for duplicate issues and we don't have to open logs to the what the problem is.

The message we have in the old editor says only we have a crash and where the log is saved.

@niels9001
Copy link
Contributor

@htcfreek Already tracked in #6984

@CDeLeon94
Copy link

I would just like to get some attention back to this post, that was marked as closed, but not actually fixed:

#1359

It is not clear, or really stated at all, how to use the subtractive editor.
Click on a template -> hit edit -> use subtractive editor -> save as custom

I think there should be a switch in the create custom, or some other way to use the subtractive that is easier to find.

@niels9001
Copy link
Contributor

@CDeLeon94 We are working on a UX overhaul. See screenshots here: #8148

Would that solve that specific issue?

@enricogior
Copy link
Contributor

enricogior commented Dec 7, 2020

@CDeLeon94 @niels9001
let's not discuss that here, this issue is not for general problems.

@gczark
Copy link

gczark commented Jan 6, 2021

In my opinion, I think it is unnecessary to include templates. Most of the templates are not usually used in daily basis. It is more intuitive and a clean experience to just have an initial zone then split, rather than showing so many options like template and number of zones to choose from.

@crutkas
Copy link
Member Author

crutkas commented Jan 6, 2021

In my opinion, I think it is unnecessary to include templates. Most of the templates are not usually used in daily basis. It is more intuitive and a clean experience to just have an initial zone then split, rather than showing so many options like template and number of zones to choose from.

Telemetry shows most people use a priority grid. More than everything else combine.

@niels9001 niels9001 changed the title [FancyZone] - Editor v2 [FancyZones] - Editor v2 Jan 12, 2021
@RCPMAD
Copy link

RCPMAD commented Feb 20, 2021

If possible the following too...
#9818
#9820

@pursuitofhoppiness
Copy link

In addition to #177, have the ability to pin an app window to a specific zone when changing environments.

For example at work (using two external monitors), I move my "always open" windows (outlook, calendar, to do, file explorer etc) to a specific zone on Monitor 3. At home, I rearrange these windows on my laptop screen, being a different size, and in a different position relative to that on Monitor 3. When I go back to work, I rearrange these windows again to Monitor 3.

@Aaron-Junker
Copy link
Collaborator

How current is this issue? Many things are already implemented.

@crutkas
Copy link
Member Author

crutkas commented Dec 25, 2021

At this point, I agree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Quality Stability, Performance, Etc. FancyZones-Editor Issue revolving the FancyZone Editor FancyZones-Layouts Issue for layouts in FancyZones Needs-Spec Something needs additional thought on how we'll implement Tracker Issue that is used to collect multiple sub-issues about a feature
Projects
None yet
Development

No branches or pull requests