Powertoys: FancyZone Issues

Created on 6 Sep 2019  路  8Comments  路  Source: microsoft/PowerToys

Hi,

  1. FancyZones doesn't support multi monitors setups. You can only edit FancyZones on the primary display. Other displays have a single zone which you can't edit.
  2. When you unsnap an application from a FancyZone, the application window should revert to it previous/original size.
  3. In some early testing I have found that some apps aren't supported properly or at all. Shift dragging Telegram (for example) doesn't bring up the FancyZones, while apps like Chrome and discord worked fine.

Ideally FancyZones should replace the default snap zones in Windows.

Product-FancyZones

Most helpful comment

+1 on the multi monitor issue. Great PowerToy but really wanted it to work with my wide screen monitor.

All 8 comments

+1 on the multi monitor issue. Great PowerToy but really wanted it to work with my wide screen monitor.

I also have the problem with the multi monitor setup and also with certain applications that are not snapping into their zones when pressing shift+drag. For example I have the problem with Edge Chromium

Chaining of issues for multi-monitor: https://github.com/microsoft/PowerToys/issues/244

For multi-monitor please check https://github.com/microsoft/PowerToys/issues/195

Ideally FancyZones should replace the default snap zones in Windows.

I feel that this should be an option as personally, I like having Windows default snap zones together with FancyZones. I've tried third party alternatives and the fact that it completely replaces Windows default snapping made me uninstall it. I think a good compromise is to add an option to change the "shift-drag" behavior between defaulting to Windows or FanzyZones snaps.

Closing this as the top issue is there and it is a multiple part issue, I do think we have a discoverabiltiy issue but we'll address that with #1032.

I created bugs for Telegram to verify and the revert to size (pretty sure there was a bug for this already but couldn't find it)

for remembering old size, #282 is the tracking issue

scratch that, #166 is the tracking issue. 282 is a dup

Was this page helpful?
0 / 5 - 0 ratings