Remove tiling gaps by default in FancyZones

[Copilot]

Changes the default spacing between tiled windows from 16 pixels to 0 pixels, eliminating gaps by default as requested by users who prefer traditional tiling window manager behavior.

Changes Made

1. Updated default spacing value

   • Changed DefaultValues::Spacing from 16 to 0 in LayoutDefaults.h
   • This affects all new layouts created with default settings

2. Improved code consistency

   • Updated isLayoutDefault() function in AppliedLayouts.cpp to use DefaultValues constants instead of hardcoded values
   • Ensures the function correctly identifies layouts using the new default spacing
   • Makes the code more maintainable for future default value changes

Behavior Changes

• Before: New FancyZones layouts had 16px gaps between windows by default
• After: New FancyZones layouts have no gaps between windows by default
• Users can still enable spacing in the FancyZones editor if desired
• Existing layouts and user preferences are preserved
• JSON parsing of existing configurations continues to work correctly

Testing

• Verified that default layouts now use 0 spacing
• Confirmed that isLayoutDefault() correctly identifies new default layouts
• Ensured backward compatibility with existing configurations
• All existing unit tests for JSON parsing functionality remain valid

This change addresses user feedback requesting the removal of default tiling gaps to match the behavior of traditional Linux tiling window managers.

Fixes #21872.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[crutkas]

is the issue, i provide a regkey i need to actively be verified. based on that reg key, when true, we should subtract -1 to the margin.

[Copilot]

is the issue, i provide a regkey i need to actively be verified. based on that reg key, when true, we should subtract -1 to the margin.

Could you clarify which specific registry key you'd like me to check? I see that PowerToys uses the GPO system for registry policies, but I'm not sure which key you're referring to for the margin adjustment functionality. Should I create a new registry key for this purpose, or is there an existing one I should use?

is the issue, i provide a regkey i need to actively be verified. based on that reg key, when true, we should subtract -1 to the margin.

I've implemented the registry key functionality for margin adjustment. Added registry key FancyZonesAdjustMargin that, when set to 1 (enabled), subtracts 1 pixel from spacing/margin values in all FancyZones layout calculations. The implementation follows PowerToys GPO policy patterns and is applied to all layout types (Grid, PriorityGrid, Rows, Columns, Custom). Commit: 0f4630e

[crutkas]

when set to 0, i need the additional -1 margin applied

HKEY_CURRENT_USER\Software\Microsoft\Windows\DWM

Look for the value: ColorPrevalence (Type: REG_DWORD)
1 = Accent color is shown on title bars and window borders
0 = Accent color is not shown

[Copilot]

when set to 0, i need the additional -1 margin applied

HKEY_CURRENT_USER\Software\Microsoft\Windows\DWM
...

Updated the implementation to use the Windows DWM ColorPrevalence registry key as requested. Now checks HKEY_CURRENT_USER\Software\Microsoft\Windows\DWM\ColorPrevalence and applies -1 margin when the value is 0 (accent color not shown). Commit: 877941a

[crutkas]

tested, no gap :)