search

microsoft / PowerToys

Windows system utilities to maximize productivity
MIT License
109.48k stars 6.45k forks source link

Certain programs (Directory Opus, Everything Search, and more) don't completely fill zones near monitor edges #30782

Open conradsrc opened 8 months ago

conradsrc commented 8 months ago

Microsoft PowerToys version

0.76.2

Installation method

WinGet

Running as admin

Yes

Area(s) with issue?

FancyZones

Steps to reproduce

  1. Create a zone layout with without "spaces around zones" (I'm actually using -2px on these screenshot'd layouts but the behavior is identical with this setting turned off completely).
  2. Snap certain programs (listed below) to one of these zones.

image

image

PowerToysReport_2024-01-06-16-14-03.zip

✔️ Expected Behavior

Window expands to fully fill the zone in the same way that the vast majority of programs do.

❌ Actual Behavior

Window has an ~8 pixel gap on 1-2 sides. As you can see from the screenshot, the ones on my bottom monitor (4K, "primary" monitor in Windows, 1.5 DPI scaling) have a gap on the right, left, and bottom ends of the screen, but not on the top (where my taskbar is). On my top monitor (1440p, 1.0 DPI scaling), it doesn't occur on the top of the screen or the bottom (where my taskbar is), but it does still happen on the left & right ends.

Other Software

Windows 11 x64 Pro (same behavior was occurring for me months ago on Windows 10 x64 Pro as well) Everything Search 1.4 and 1.5a Directory Opus 12.33 RemoveEmptyDirectories 2.2.0.0 nVIDIA Profile Inspector 2.4.0.4 ShellMenuView 1.4 ShellExView 2.01

airdmo commented 6 months ago

I have the same problem Directory Opus 13.3 PowerToys0.78

Directory Opus cannot snap to the left or right edge of the screen will leave a gap

conradsrc commented 3 months ago

Here's one program I recently noticed it on that may be worth mentioning: The Windows Control Panel!

This native program (using one of the many past-era UIs still accessible in Win11) is exhibiting the exact same behavior. It kinda looks like it's using some old Win7-era version of Windows Explorer? Obviously the current Win11 Windows Explorer doesn't do it but the Control Panel seems like a fairly significant program to affect. And maybe it being Microsoft code would make it easier for someone to diagnose what DWM setting/API call (?) causes this behavior.