Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FancyZones: Override default Windows Maximize/Restore behaviour and apply it on underlying zone instead of the monitor #25574

Closed
papadi opened this issue Apr 17, 2023 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@papadi
Copy link

papadi commented Apr 17, 2023

Description of the new feature / enhancement

I believe that when hitting the Max/Restore icon of a window or when double-clicking on the title bar, the window should get maximized or restored in the underlying zone and not in the underlying window, which is of course the Windows default behaviour unless the user presses and holds the shift key.

Scenario when this would be used?

I should not need to click and drag a window to maximize it in the underlying zone. Hitting the Maximize button or double-clicking the title bar should be enough.

Supporting information

This is the default behaviour of DisplayFusion which I'm trying to replace.

@papadi papadi added the Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams label Apr 17, 2023
@stefansjfw
Copy link
Collaborator

/dup #24263

@microsoft-github-policy-service
Copy link
Contributor

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Apr 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants