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

Workspaces Editor window upon open does not remember size or placement #35238

Closed
SparksFlyn opened this issue Oct 3, 2024 · 8 comments
Closed
Assignees
Labels
Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Product-Workspaces Refers to the Workspaces utility Resolution-Fix Committed Fix is checked in, but it might be 3-4 weeks until a release.

Comments

@SparksFlyn
Copy link

Description of the new feature / enhancement

The Workspace Editor window opens on my Dell 49" monitor as a wide window that does not seem to honor my Fancy Zone settings. I resize the Workspace Editor window to a smaller and narrower window, but does not remember the sizing or placement. Otherwise, liking the PowerToy Workspaces. I have two Dell 49" monitors stack one on top of the other. Workspaces works well at placing my selected apps after opening on the two monitors.

Scenario when this would be used?

Workspaces Editor works well at remembering the apps and window positions when I create a workspace. Maybe I need to create a workspace for Workspace Editor so that it will reopen with settings I create.

Supporting information

No response

@SparksFlyn SparksFlyn added the Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams label Oct 3, 2024
@davidegiacometti davidegiacometti added the Product-Workspaces Refers to the Workspaces utility label Oct 3, 2024
@Kronopt
Copy link

Kronopt commented Nov 5, 2024

I second this.

The Workspaces Editor windows does not remember window size and placement

@donlaci donlaci self-assigned this Nov 27, 2024
@donlaci donlaci added the Resolution-Fix Committed Fix is checked in, but it might be 3-4 weeks until a release. label Nov 27, 2024
@donlaci
Copy link
Collaborator

donlaci commented Nov 27, 2024

#36086 solves this

@donlaci
Copy link
Collaborator

donlaci commented Dec 17, 2024

@SparksFlyn please retest with the new 0.87 PT version and if the issue persists send a /bugreport. Thanks!

@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 Dec 17, 2024
Copy link
Contributor

Hi there!

We need a bit more information to really debug this issue. Can you add a "Report Bug" zip file here? You right click on our system tray icon and just go to report bug. Then drag the zipfile from your desktop onto the GitHub comment box in this issue. Thanks!
Report Bug

@Kronopt
Copy link

Kronopt commented Dec 18, 2024

@donlaci, thank you for your Pull Request.

I tested it just now and it worked ok. Existing windows for programs are resized and moved to the correct position (as far as I tested).

I just found an issue that I don't know if it's intended behavior or not: When one of the programs that already has an existing window is Google Chrome, a new window is opened instead of using the existing one. It still gets resized and moved correctly, but it's not the existing window that does it

@donlaci
Copy link
Collaborator

donlaci commented Dec 18, 2024

@Kronopt

Thanks for your feedback. I will close this issue as solved and you might open a new one for the new issue.
I suppose you have checked the "Move existing windows" checkbox in the editor and that moving works for other apps except Chrome.
Beware of duplicates and please include also a bugreport if the issue persists. Thanks for your cooperation!

@donlaci donlaci closed this as completed Dec 18, 2024
@Kronopt
Copy link

Kronopt commented Dec 19, 2024

Ah! I didn't notice that checkbox!
It's working as intended now! My bad!

Thank you! :)

@SparksFlyn
Copy link
Author

SparksFlyn commented Jan 3, 2025

This is working as desired. However, I did notice that the installation of a new PT release resets the Workspace Editor to default size and placement. I have to resize it once again after installing a new PT release. I will wait until a new PT release to confirm that persistence is not happening. Workspaces is working better with Chrome if one is using profiles. Opening Chrome would first pop up with the profile selection page and then go on to open the main browser page. The Chrome browser opening is opening at the desired position for me now.

PT v0.87.1 installed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Product-Workspaces Refers to the Workspaces utility Resolution-Fix Committed Fix is checked in, but it might be 3-4 weeks until a release.
Projects
None yet
Development

No branches or pull requests

4 participants