Fancy Zones change on all monitors when changing the resolution on one monitor

tomauPFE commented 3 years ago

Microsoft PowerToys version

0.47.0

Running as admin

[ ] Yes

Area(s) with issue?

FancyZones

Steps to reproduce

Set up no Zones on monitor 1 and two equal zones on monitor 2. Change the resolution on Monitor 1 to 1920x1080 and the Zones change on both monitors.

✔️ Expected Behavior

Zones should not change when changing monitor resolution. This worked fine until I upgraded to Windows 11.

❌ Actual Behavior

I have Fancy Zones set up with no zones on one monitor and two equal vertical zones on the second monitor. When I change resolution on the monitor with no zones to a lower resolution it adds zones to that monitor and removes the two zones from the second monitor and adds back three zones.

Other Software

No response

HeliosAnavatis commented 3 years ago

I'm having something similar - I use 2 monitors; monitor 1 is landscape-mode 3840x2160 and monitor 2 is portrait mode 1024x1280. Monitor 1 often switches between other computers but whenever I log in to my Windows machine, the fancy zones on both monitors have reset back to "Priority Grid" from my custom layouts. This has only started happening since the most recent update. I'm on v0.47.0 on Windows 10 19043.1266

mitchgeek commented 3 years ago

Hi there. I am having the same issue as this on windows 11. every morning I log in it reverts back to priority grid. I have one monitor.

mmulhearn commented 3 years ago

I'm having a similar issue. It was working earlier today. Shut down for a few hours and booted back up and I'm stuck in priority grid (I prefer columns). When I changed it, it dumped an error file:


## Exception

System.ComponentModel.Win32Exception: Invalid window handle. Source: WindowsBase TargetAssembly: WindowsBase, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 TargetModule: WindowsBase.dll TargetSite: Void HookUpDefWindowProc(IntPtr) at MS.Win32.ManagedWndProcTracker.HookUpDefWindowProc(IntPtr hwnd) at MS.Win32.ManagedWndProcTracker.OnAppDomainProcessExit() at MS.Win32.ManagedWndProcTracker.ManagedWndProcTrackerShutDownListener.OnShutDown(Object target, Object sender, EventArgs e) at MS.Internal.ShutDownListener.HandleShutDown(Object sender, EventArgs e) at System.AppContext.OnProcessExit()


## Environment
* Command Line: "C:\Program Files\PowerToys\modules\FancyZones\FancyZonesEditor.dll" 11748/0/SAM7053#5&2af624bb&0&UID4354_5120_1440_{F60FD56C-C3CF-4399-894F-9BEBC3392196}/1/SAM7053#5&2af624bb&0&UID4354_5120_1440_{F60FD56C-C3CF-4399-894F-9BEBC3392196}/96/0/0/5120/1392/
* Timestamp: 10/07/2021 19:41:20
* OS Version: Microsoft Windows NT 6.2.9200.0
* IntPtr Length: 8
* x64: True
* CLR Version: 3.1.19
## Assemblies - FancyZonesEditor

* System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Private.CoreLib.dll)
* FancyZonesEditor, Version=0.47.0.0, Culture=neutral, PublicKeyToken=null (C:\Program Files\PowerToys\modules\FancyZones\FancyZonesEditor.dll)
* PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 (C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.19\PresentationFramework.dll)
* WindowsBase, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 (C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.19\WindowsBase.dll)
* System.Runtime, Version=4.2.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Runtime.dll)
* System.Xaml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 (C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.19\System.Xaml.dll)
* System.ObjectModel, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.ObjectModel.dll)
* System.Threading.Thread, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Threading.Thread.dll)
* System.IO.Packaging, Version=4.0.5.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.19\System.IO.Packaging.dll)
* netstandard, Version=2.1.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51 (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\netstandard.dll)
* System.Private.Uri, Version=4.0.6.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Private.Uri.dll)
* PresentationCore, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 (C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.19\PresentationCore.dll)
* System.Linq, Version=4.2.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Linq.dll)
* System.Collections, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Collections.dll)
* System.Runtime.Extensions, Version=4.2.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Runtime.Extensions.dll)
* System.Threading, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Threading.dll)
* Microsoft.Win32.Registry, Version=4.1.3.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\Microsoft.Win32.Registry.dll)
* System.Diagnostics.Debug, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Diagnostics.Debug.dll)
* System.Collections.Specialized, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Collections.Specialized.dll)
* System.ComponentModel.Primitives, Version=4.2.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.ComponentModel.Primitives.dll)
* System.Diagnostics.Process, Version=4.2.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Diagnostics.Process.dll)
* Microsoft.Win32.Primitives, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\Microsoft.Win32.Primitives.dll)
* System.Collections.NonGeneric, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Collections.NonGeneric.dll)
* System.Runtime.InteropServices, Version=4.2.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Runtime.InteropServices.dll)
* System.Configuration.ConfigurationManager, Version=4.0.3.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51 (C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.19\System.Configuration.ConfigurationManager.dll)
* System.Xml.ReaderWriter, Version=4.2.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Xml.ReaderWriter.dll)
* System.Private.Xml, Version=4.0.2.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51 (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Private.Xml.dll)
* System.IO.FileSystem, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.IO.FileSystem.dll)
* System.Net.WebClient, Version=4.0.2.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51 (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Net.WebClient.dll)
* System.Memory, Version=4.2.1.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51 (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Memory.dll)
* System.Security.Cryptography.Algorithms, Version=4.3.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Security.Cryptography.Algorithms.dll)
* System.Text.Encoding.Extensions, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Text.Encoding.Extensions.dll)
* System.Resources.ResourceManager, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Resources.ResourceManager.dll)
* System.Threading.Tasks, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Threading.Tasks.dll)
* System.IO.Abstractions, Version=12.0.0.0, Culture=neutral, PublicKeyToken=96bf224d23c43e59 (C:\Program Files\PowerToys\modules\FancyZones\System.IO.Abstractions.dll)
* System.Text.Json, Version=5.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51 (C:\Program Files\PowerToys\modules\FancyZones\System.Text.Json.dll)
* System.Security.AccessControl, Version=4.1.3.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Security.AccessControl.dll)
* System.Collections.Concurrent, Version=4.0.15.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Collections.Concurrent.dll)
* PowerToysInterop, Version=0.47.0.0, Culture=neutral, PublicKeyToken=null (C:\Program Files\PowerToys\modules\FancyZones\PowerToysInterop.dll)
* mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\mscorlib.dll)
* System.Threading.ThreadPool, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Threading.ThreadPool.dll)
* System.Diagnostics.TraceSource, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Diagnostics.TraceSource.dll)
* System.ComponentModel.TypeConverter, Version=4.2.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.ComponentModel.TypeConverter.dll)
* System.Windows.Extensions, Version=4.0.1.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51 (C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.19\System.Windows.Extensions.dll)
* System.ComponentModel, Version=4.0.4.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.ComponentModel.dll)
* ModernWpf, Version=0.9.4.0, Culture=neutral, PublicKeyToken=null (C:\Program Files\PowerToys\modules\FancyZones\ModernWpf.dll)
* Windows.UI, Version=255.255.255.255, Culture=neutral, PublicKeyToken=null, ContentType=WindowsRuntime (C:\WINDOWS\system32\WinMetadata\Windows.UI.winmd)
* Windows.Foundation, Version=255.255.255.255, Culture=neutral, PublicKeyToken=null, ContentType=WindowsRuntime (C:\WINDOWS\system32\WinMetadata\Windows.Foundation.winmd)
* System.Runtime.WindowsRuntime, Version=4.0.15.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Runtime.WindowsRuntime.dll)
* System.Runtime.InteropServices.WindowsRuntime, Version=4.0.4.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Runtime.InteropServices.WindowsRuntime.dll)
* Microsoft.Win32.SystemEvents, Version=4.0.2.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51 (C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.19\Microsoft.Win32.SystemEvents.dll)
* System.Net.Requests, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Net.Requests.dll)
* System.Net.Primitives, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Net.Primitives.dll)
* System.Security.Principal, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Security.Principal.dll)
* System.Net.WebHeaderCollection, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Net.WebHeaderCollection.dll)
* PresentationFramework.Aero2, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 (C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.19\PresentationFramework.Aero2.dll)
* ManagedCommon, Version=0.47.0.0, Culture=neutral, PublicKeyToken=null (C:\Program Files\PowerToys\modules\FancyZones\ManagedCommon.dll)
* Microsoft.PowerToys.Common.UI, Version=0.47.0.0, Culture=neutral, PublicKeyToken=null (C:\Program Files\PowerToys\modules\FancyZones\Microsoft.PowerToys.Common.UI.dll)
* System.Diagnostics.StackTrace, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Diagnostics.StackTrace.dll)
* ManagedTelemetry, Version=0.47.0.0, Culture=neutral, PublicKeyToken=null (C:\Program Files\PowerToys\modules\FancyZones\ManagedTelemetry.dll)
* System.Diagnostics.Tracing, Version=4.2.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Diagnostics.Tracing.dll)
* ControlzEx, Version=4.0.0.0, Culture=neutral, PublicKeyToken=69f1c32f803d307e (C:\Program Files\PowerToys\modules\FancyZones\ControlzEx.dll)
* PresentationFramework-SystemXml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 (C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.19\PresentationFramework-SystemXml.dll)
* System.Drawing.Primitives, Version=4.2.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Drawing.Primitives.dll)
* System.ComponentModel.EventBasedAsync, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.ComponentModel.EventBasedAsync.dll)
* System.Buffers, Version=4.0.5.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51 (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Buffers.dll)
* System.Text.Encodings.Web, Version=5.0.0.1, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51 (C:\Program Files\PowerToys\modules\FancyZones\System.Text.Encodings.Web.dll)
* System.Runtime.Intrinsics, Version=4.0.1.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51 (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Runtime.Intrinsics.dll)
* System.Reflection.Emit.Lightweight, Version=4.1.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Reflection.Emit.Lightweight.dll)
* System.Reflection.Emit.ILGeneration, Version=4.1.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Reflection.Emit.ILGeneration.dll)
* System.Reflection.Primitives, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Reflection.Primitives.dll)
* System.Runtime.CompilerServices.Unsafe, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\PowerToys\modules\FancyZones\System.Runtime.CompilerServices.Unsafe.dll)
* System.Numerics.Vectors, Version=4.1.6.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Numerics.Vectors.dll)
* UIAutomationTypes, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 (C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.19\UIAutomationTypes.dll)
* DirectWriteForwarder, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 (C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.19\DirectWriteForwarder.dll)
* System.Runtime.CompilerServices.VisualC, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Runtime.CompilerServices.VisualC.dll)
* UIAutomationProvider, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 (C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.19\UIAutomationProvider.dll)
* ModernWpf.Controls, Version=0.9.4.0, Culture=neutral, PublicKeyToken=null (C:\Program Files\PowerToys\modules\FancyZones\ModernWpf.Controls.dll)
* System.Windows.Controls.Ribbon, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 (C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.19\System.Windows.Controls.Ribbon.dll)
* WindowsFormsIntegration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 (C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.19\WindowsFormsIntegration.dll)
* System.Reflection.Metadata, Version=1.4.5.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Reflection.Metadata.dll)
* System.Collections.Immutable, Version=1.2.5.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.19\System.Collections.Immutable.dll)

franky920920 commented 3 years ago

I'm having a similar issue. It was working earlier today. Shut down for a few hours and booted back up and I'm stuck in priority grid (I prefer columns). When I changed it, it dumped an error file:

Your error is tracked in #13105

mmulhearn commented 3 years ago

I'm having a similar issue. It was working earlier today. Shut down for a few hours and booted back up and I'm stuck in priority grid (I prefer columns). When I changed it, it dumped an error file:

Your error is tracked in #13105

That doesn't describe my issue. The editor shows up, it just errors when I set a new layout.

One thing I noticed is that if I use the global shortcut it errors. If I open powertoys from the start bar and go into Fancy Zones from there, it works. Not sure what the difference is, but that seems to be the case.

svboyko commented 3 years ago

I've the similar issue.

Brief description

second monitor connected to notebook
monitors have different resolutions
second monitor set as a main windows display
multiple displays mode: Extend
custom Fancy zone layout set for second monitor (which configured as main windows display)

Actual behavior:

after each sleep/awake Fancy Zones layout switches from my custom layout to "Priority Grid" layout for my second monitor (main window display)

Estimated behavior:

system should keep Fancy Zones layout that set for monitor

Notes:

the internal notebook monitor (which configured as extended windows display) also changes his layout to "Priority Grid" after sleep/awake
i've tried to disable "Quick layout switch" - it does not help
this bug appeared after updating from v.0.45.0 to v0.47.0

woutervanranst commented 3 years ago

Same issue here with 5120x1440 - after resume from sleep goes back to priority grid

franky920920 commented 3 years ago

Same issue here with 5120x1440 - after resume from sleep goes back to priority grid

You're issue is tracked in #13625

crutkas commented 3 years ago

I'd like to call a time out for +1'ing. This issue right now seems to be a combo of a different items with people adding i have an issue.

Please create new issues and let the PowerToy team group. What may look the same or different to you, the logs really do help direct what we do. Also lets us clearly know what versions we're dealing with as with 47.1, we do have some fixes in place.

@tomauPFE can you add some logs? you can create them via system tray.

crutkas commented 3 years ago

Also have you tried 0.47.1 as this was reported with 0.45

tomauPFE commented 3 years ago

It looks like the issue for me at least has been resolved. I changed my display settings twice and the layouts didn’t change. Just in case I have attached the report.

Tom Ausburne Customer Engineer US National CSU Mobile: 704-222-7612 @.**@.>

[Microsoft] If I have helped you in any way and you would like to send Kudos please go here. Kudoshttps://apps.powerapps.com/play/providers/Microsoft.PowerApps/apps/0a71d7d0-5325-6898-afd2-4f3498d98bf6?&authMode=Default

From: Clint Rutkas @.> Sent: Friday, October 15, 2021 1:07 PM To: microsoft/PowerToys @.> Cc: Tom Ausburne @.>; Mention @.> Subject: Re: [microsoft/PowerToys] Fancy Zones change on all monitors when changing the resolution on one monitor (#13684) Importance: High

I'd like to call a time out for +1'ing. This issue right now seems to be a combo of a different items with people adding i have an issue.

Please create new issues and let the PowerToy team group. What may look the same or different to you, the logs really do help direct what we do. Also lets us clearly know what versions we're dealing with as with 47.1, we do have some fixes in place.

@tomauPFEhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FtomauPFE&data=04%7C01%7Ctomau%40microsoft.com%7Cf2f35454bf0c4b9b7b7208d98ffe25c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637699143999489676%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3dx2J7sAKa2jcEDADvSswTPaHHXhKSRQvK54xtHgCJw%3D&reserved=0 can you add some logs? you can create them via system tray. [image]https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F1462282%2F137526022-55b1500a-2ab2-4f43-aff7-679e8bec0180.png&data=04%7C01%7Ctomau%40microsoft.com%7Cf2f35454bf0c4b9b7b7208d98ffe25c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637699143999489676%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=%2BNVXoMHgTjsBea5B0oQNtjrl%2Fgcd8%2FN0CrlaTLYecQ8%3D&reserved=0

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FPowerToys%2Fissues%2F13684%23issuecomment-944458682&data=04%7C01%7Ctomau%40microsoft.com%7Cf2f35454bf0c4b9b7b7208d98ffe25c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637699143999499670%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=m1nGEbEjcLjmUc7Bgiwo3sQzqkkfVjHYSlNeAENCowI%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMSFQWDD4OYBMR2N7ZBMYXTUHBNRZANCNFSM5FRXSV6Q&data=04%7C01%7Ctomau%40microsoft.com%7Cf2f35454bf0c4b9b7b7208d98ffe25c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637699143999509663%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3XXzRksvO9J%2FdGks2OtNptmOvziZ2gqpah4W%2FqKp4PA%3D&reserved=0. Triage notifications on the go with GitHub Mobile for iOShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04%7C01%7Ctomau%40microsoft.com%7Cf2f35454bf0c4b9b7b7208d98ffe25c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637699143999509663%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=9AbgUV9nKYwZfNUiHn3l12uFfP8L8H%2FDNJh20VZngc4%3D&reserved=0 or Androidhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04%7C01%7Ctomau%40microsoft.com%7Cf2f35454bf0c4b9b7b7208d98ffe25c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637699143999519660%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Ulpm1oaGmX1Vez61%2Fjp9Q86xgKRbbPkIEixhdogOauA%3D&reserved=0.

tomauPFE commented 3 years ago

I just sent the reply that I was upgraded to 0.47.1 and the issue seems to have been resolved.

Thanks,

Tom Ausburne Customer Engineer US National CSU Mobile: 704-222-7612 @.**@.>

[Microsoft] If I have helped you in any way and you would like to send Kudos please go here. Kudoshttps://apps.powerapps.com/play/providers/Microsoft.PowerApps/apps/0a71d7d0-5325-6898-afd2-4f3498d98bf6?&authMode=Default

From: Clint Rutkas @.> Sent: Friday, October 15, 2021 1:07 PM To: microsoft/PowerToys @.> Cc: Tom Ausburne @.>; Mention @.> Subject: Re: [microsoft/PowerToys] Fancy Zones change on all monitors when changing the resolution on one monitor (#13684) Importance: High

Also have you tried 0.47.1 as this was reported with 0.45

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FPowerToys%2Fissues%2F13684%23issuecomment-944458915&data=04%7C01%7Ctomau%40microsoft.com%7Ca3cb4280502b49c5945e08d98ffe332f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637699144226648237%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qpz4O4QhmrXU1kvVW%2Fi7Gox2Xn66PXO7RDnruVZt%2FBQ%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMSFQWBKIPMUICGW3QG5GVDUHBNTHANCNFSM5FRXSV6Q&data=04%7C01%7Ctomau%40microsoft.com%7Ca3cb4280502b49c5945e08d98ffe332f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637699144226658232%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=gcbde%2Bk%2BNyDWhgPoEKUsHTXlsJW3mnX9Bj3F62P2I0M%3D&reserved=0. Triage notifications on the go with GitHub Mobile for iOShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04%7C01%7Ctomau%40microsoft.com%7Ca3cb4280502b49c5945e08d98ffe332f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637699144226668232%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=pppjfr3ItPy%2Fuvckd6%2F4OCv%2BndeHT66e5B%2BXKhA%2Fw%2Bw%3D&reserved=0 or Androidhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04%7C01%7Ctomau%40microsoft.com%7Ca3cb4280502b49c5945e08d98ffe332f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637699144226678225%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=hyMQqBmqNnAFTtaHSmbIu01a3EmgznoU4du7xifn7rg%3D&reserved=0.

crutkas commented 3 years ago

Good to hear the issue is fixed with the latest. If anyone is having issues past 0.47.1, please file a new issue and having a bug zip file is super helpful.

mitchgeek commented 3 years ago

Seems to be resolved. Thanks.

Regards Mitch

From: Clint Rutkas @.> Sent: Saturday, October 16, 2021 4:06:59 AM To: microsoft/PowerToys @.> Cc: mitchgeek @.>; Comment @.> Subject: Re: [microsoft/PowerToys] Fancy Zones change on all monitors when changing the resolution on one monitor (#13684)

Also have you tried 0.47.1 as this was reported with 0.45

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerToys/issues/13684#issuecomment-944458915, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APVXG3MOP5MOFYI3PIWBMYLUHBNTHANCNFSM5FRXSV6Q. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

microsoft / PowerToys