Powertoys: Win+arrow not overriding Aerosnap

[pmarsh]

Environment

Windows build number: 1903 
PowerToys version: 0.11.0
PowerToy module for which you are reporting the bug (if applicable): FancyZones

4K monitor set as primary montior hooked up to Surface Pro 4

Steps to reproduce

Turn on "Override Windows Snap hotkeys...

Expected behavior

Win+arrow moves windows between FancyZones and not snap them to different positions as normal

Actual behavior

Windows are moving per regular Windows snapping rules. Attempts at turning the setting on and off & restarting fancy zones has no effect.

[enricogior]

Hi @pmarsh
I've tried to reproduce the problem you described, but it seems to work fine for me.
Can you please make sure FancyZones is set to on in the General Settings?
Thank you.

[pmarsh]

@enricogior FancyZones itself works with the normal hold shift and drag option. I tried turning it off, exiting PowerToys, and back on but still no luck.

Here are my settings

• On: Hold Shift key to enable zones while draggin
• On: Override Windows Snap hotkeys
• On: Flash zones
• On: Keep windows in their zones
• Off: Keep windows in zones when the active layout changes
• Off: Keep windows pinned to multiple desktops
• On: Move newly created windows to last known zone
• On: Use new zone editing experience

[enricogior]

Thanks for the extra infos.

[enricogior]

Hi @pmarsh
have you tried the latest 0.13.0 release? The FZ snapping is still not working for you?
Thank you.

[pmarsh]

@enricogior Nope. Fresh install tried turning on/off the setting for Override as well.

I created a custom layout with 6 zones. Didn't work there either.

[pmarsh]

@enricogior Quick follow-up, the snap override feature works when the Surface is not connected to the second monitor. Again the second 4K monitor is set to Primary and the Surface built-in screen is not active as a second monitor.

[enricogior]

@pmarsh
I tried to reproduce the issue using a generic laptop, turning off the built-in screen and only using the external 4K monitor connected via HDMI, and it worked as expected.
It may be an issue specific of the Surface, what exact model it's your Surface?

[DavidGretzschel]

0.13
Also on a 4k monitor. I'm observing that sometimes the win+snap goes back to normal behaviour.

I actually wish that there was a way to use both normal behaviour and the grid, somehow.
Quarting in Windows 10 is a genuinely useful tool, that I'd wish to make use out of both my grid and the default halving/quartering functionality.

[enricogior]

@DavidGretzschel
please open a new issue to propose a change so both Windows Snap and FancyZones Snap can work at the same time.

[DavidGretzschel]

@enricogior
https://github.com/microsoft/PowerToys/issues/770
I already consider that an undocumented feature. Though when I wrote here, I didn't understand it yet.
What pmarsh is dealing with seems to be a seperate issue.
@pmarsh could you look at my video and confirm that it isn't the same?

[enricogior]

@DavidGretzschel
OK thanks.

[pmarsh]

@enricogior I isolated the issue, maybe you can replicate it.

I never assumed it would be my USB connected external keyboard causing the issue. It is an Kinesis Advantage keyboard connected to a Surface Dock for complete clarity.

However, I have found if using the directly attached Surface Keyboard win+arrows the snapping to Zones works as expected.

@DavidGretzschel Thanks for the video, I can confirm that is what happens when using the Surface keyboard. Which is good obviously haha.

I'll dig up a second USB keyboard and see if the other behavoir still happens or if it is unique to the Kinesis.

[enricogior]

Hi @pmarsh
thanks for the update. So since this is not caused by the software I'm closing the issue as external, OK?
Thanks.

[theaquamarine]

Hi,

Can this please be reopened? It's not keyboard-specific: FancyZones only responds to VK_LWIN but the Kinesis Advantage referenced only has a right-side Windows key that sends VK_RWIN by default. The same behaviour can be seen using a keyboard that has two Windows keys, etc.

I've not looked hard but I suspect the issue is here only checking VK_LWIN status.