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

display current initialPosition/initialRows/initialCols #4730

Closed
bruceoberg opened this issue Feb 26, 2020 · 2 comments
Closed

display current initialPosition/initialRows/initialCols #4730

bruceoberg opened this issue Feb 26, 2020 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@bruceoberg
Copy link

Description of the new feature/enhancement

After the window position and size has been adjusted manually, I'd like to know exactly which numbers to set for initialPosition, initialRows, and initialCols in my profile. That is, I want to adjust my window by hand and then restore to that later.

Proposed technical implementation details (optional)

Hard to say... I just want to see the numbers. Perhaps some text in the about box? Or some commented out text in settings.json so that I can uncomment it to restore the window?

(Note that this is related to #4620 where I want to set the numbers from the command line. I need a way to adjust the window and get the numbers for my command line parameters, if that is ever offered).

@bruceoberg bruceoberg added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Feb 26, 2020
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Feb 26, 2020
@DHowett-MSFT
Copy link
Contributor

Sorry for taking so long -- I've been deliberating about what the best thing to do with this feature request is. First off: thanks for filing it! I think it's worthwhile.

I feel like this is something we're going to tackle more holistically with the status bar (#3459), which could display things like the current window/pane size, and a floating drag indicator that shows where the window is/how big it is while you're moving it around. I'd prefer to use those as more natural affordances than finding somewhere in the UI to stick ephemeral data like this.

I toyed with a couple other ideas:

  1. a way to copy a JSON blob for the active configuration
  2. A way to commit the active settings as default (Feature Request: Save current config as Initial #1056)

At the end of the day, though, this'll be helped immensely by the settings UI (#1564) ... so I'm going to close it out.

In favor of one of those three bugs: this is either behavior that would be encompassed by, or a /dupe of #1056 #3459 and #1564.

Thanks!

@ghost
Copy link

ghost commented Apr 10, 2020

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!

@ghost ghost closed this as completed Apr 10, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Apr 10, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. 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