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] Workspaces Editor should remember it's window size (and position) #34623

Closed
detlefs opened this issue Sep 5, 2024 · 7 comments
Closed
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@detlefs
Copy link

detlefs commented Sep 5, 2024

Description of the new feature / enhancement

When opening the workspace editor, it always opens the same big window in the center of the screen. The big size is not necessary and users may have different preferences. So if user resizes the window, this should be remembered when the window is opened next time.

Scenario when this would be used?

Whenever starting or editing a workspace

Supporting information

Current behavior may be more annoying on big screens than on small screens. For me the window is always opened like 90% empty

@detlefs detlefs added the Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams label Sep 5, 2024
@bergamin
Copy link

bergamin commented Sep 5, 2024

I didn't see your post at first, but I opened another issue with a suggestion on how they could do that: #34636

@plante-msft plante-msft added the Product-Workspaces Refers to the Workspaces utility label Sep 6, 2024
@donlaci
Copy link
Collaborator

donlaci commented Dec 18, 2024

@detlefs 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 18, 2024
@donlaci donlaci removed 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 labels Dec 18, 2024
@bergamin
Copy link

@detlefs, Most windows opened in the correct places, except for the following:

I know Workspaces positioning worked on the windows that went to the correct places because 7Pace, which normally opens in the middle of the screen, opened at its designated place

@SeraphimaZykova
Copy link
Collaborator

This sounds like a /dup #36034.

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 the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Dec 30, 2024
@bergamin
Copy link

bergamin commented Jan 7, 2025

@SeraphimaZykova, that one is newer than this one. So that one might be a duplicate of this and not the other way round...

That being said, Toggl Track still launches at the wrong position. I'm on v0.87.1

@SeraphimaZykova
Copy link
Collaborator

@SeraphimaZykova, that one is newer than this one. So that one might be a duplicate of this and not the other way round...

Thank you for your comment. The issue I referred to is linked to an existing pull request that addresses it, so I duplicated this issue. In this case, the order in which they were opened is irrelevant.

That being said, Toggl Track still launches at the wrong position. I'm on v0.87.1

Please open a separate issue for Toggl Track, as it's not related to the current issue. Thank you!

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

5 participants