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

FancyZone - Layout Type Mismatch: Columns Saved as Grid #36649

Open
jjdevzinho opened this issue Dec 30, 2024 · 2 comments
Open

FancyZone - Layout Type Mismatch: Columns Saved as Grid #36649

jjdevzinho opened this issue Dec 30, 2024 · 2 comments
Labels
Issue-Bug Something isn't working Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams

Comments

@jjdevzinho
Copy link

Microsoft PowerToys version

0.87.1

Installation method

Microsoft Store

Running as admin

Yes

Area(s) with issue?

FancyZones

Steps to reproduce

  1. Open the FancyZones editor.

  2. Select or create a layout of type columns.

  3. Save the layout.

  4. Check the JSON file for custom layouts at %UserProfile%\AppData\Local\Microsoft\PowerToys\FancyZones\custom-layouts.json.

✔️ Expected Behavior

The layout of type columns should be saved as columns in the type field of the JSON file

❌ Actual Behavior

The layout of type columns is being saved as grid in the type field of the JSON file.

Other Software

No response

@jjdevzinho jjdevzinho added Issue-Bug Something isn't working Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Dec 30, 2024
Copy link

We've found some similar issues:

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@jjdevzinho
Copy link
Author

Furthermore, we would like to understand if there are functional differences between the various layout types (columns, grid, priority-grid, etc.) or if all are treated merely as canvas and grid internally. This apparent redundancy and confusion regarding the layout types available in the interface versus how they are saved and handled in the backend needs clarification

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug Something isn't working Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams
Projects
None yet
Development

No branches or pull requests

1 participant