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

Multi-screen FancyZones lay-out #27938

Open
Dontrader opened this issue Aug 10, 2023 · 5 comments
Open

Multi-screen FancyZones lay-out #27938

Dontrader opened this issue Aug 10, 2023 · 5 comments
Labels
Needs-Team-Response An issue author responded so the team needs to follow up Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams Product-FancyZones Refers to the FancyZones PowerToy

Comments

@Dontrader
Copy link

Description of the new feature / enhancement

The possibility for a FancyZones Lay-out that spans multiple screens (or at least 2).

Scenario when this would be used?

I would like my browser window to span (part of) both my two screens. Now I have to manually drag the side of the browser to expand it to two screens. Would be much easier if my browser could just snap to the multiscreen lay-out.

Supporting information

No response

@Dontrader Dontrader added the Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams label Aug 10, 2023
@davidegiacometti
Copy link
Collaborator

Have you tried these settings yet?

Screenshot 2023-08-12 105017

/needinfo

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something and removed Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Aug 12, 2023
@microsoft-github-policy-service
Copy link
Contributor

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment.

@microsoft-github-policy-service microsoft-github-policy-service bot added the Status-No recent activity no activity in the past 5 days when follow up's are needed label Aug 17, 2023
@Dontrader
Copy link
Author

Dontrader commented Aug 17, 2023 via email

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams Needs-Team-Response An issue author responded so the team needs to follow up and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Status-No recent activity no activity in the past 5 days when follow up's are needed labels Aug 17, 2023
@nguyen-dows
Copy link

Hey @Dontrader, does that option resolve your issues? If so I will close this issue in a few days.
Thanks in advance!

@nguyen-dows nguyen-dows added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Product-FancyZones Refers to the FancyZones PowerToy and removed Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams Needs-Team-Response An issue author responded so the team needs to follow up labels Nov 15, 2024
@Dontrader
Copy link
Author

Dontrader commented Nov 16, 2024 via email

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams Needs-Team-Response An issue author responded so the team needs to follow up and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Nov 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Team-Response An issue author responded so the team needs to follow up Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams Product-FancyZones Refers to the FancyZones PowerToy
Projects
Status: No status
Development

No branches or pull requests

3 participants