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

Reload should preserve maximized panel #79891

Closed
isidorn opened this issue Aug 27, 2019 · 8 comments · Fixed by microsoft/azuredatastudio#7356
Closed

Reload should preserve maximized panel #79891

isidorn opened this issue Aug 27, 2019 · 8 comments · Fixed by microsoft/azuredatastudio#7356
Assignees
Labels
layout General VS Code workbench layout issues

Comments

@isidorn
Copy link
Contributor

isidorn commented Aug 27, 2019

Refs: #79845

  1. Maximize the panel
  2. Reload
  3. Panel is not maximized 🐛

Marking as a feature request since we never had this feature since panel could never be full height.
The ugly part about this flow is that we forget the previous size of the panel before the user maximized it (so he can not go back with a click)

@isidorn isidorn added the layout General VS Code workbench layout issues label Aug 27, 2019
@isidorn
Copy link
Contributor Author

isidorn commented Aug 27, 2019

Also instread of reload you can toggle panel visibility via ctrl/cmd + j. That should aslo preserve the maximized panel

@sbatten
Copy link
Member

sbatten commented Aug 27, 2019

hmm, thanks for the feedback. The benefit of today's behavior is that if a user accidentally hides the editor and can't get it back, a reload will always reset it and I don't anticipate a lot of people leaving the editor hidden across sessions. Also imagine the following scenario regarding your second point.

  1. I maximize the terminal to do some work. (The goal being to see the terminal, not hide the editor)
  2. I then hide the terminal to get back to coding. This shows the editor and feels right from the user's perspective.
  3. I then show the terminal again for a quick command. Do I necessarily want the editor to be gone? I don't really know the answer to this, but I feel like the answer is no.

@sbatten sbatten added this to the August 2019 milestone Aug 27, 2019
@sbatten
Copy link
Member

sbatten commented Aug 27, 2019

one thing I should probably do and might feel better is make sure that if we do bring the editor back from a hidden state on restore, the panel is not almost maximized but rather its previous unmaximized state

@isidorn
Copy link
Contributor Author

isidorn commented Aug 28, 2019

Agree that the panel in a not almost maximized state never makes sense since the user looses the previous unmaximized state.

However I would still prefer that the panel remains maximized. Since the user can always click on the editor in the explorer / open editors view / quick pick and to get out of this mode. And you handle it already very nicely. So I am not worried about user being stuck at all.

Though I would love to hear the opinion from @Tyriar since he is very passionate about this

@sbatten
Copy link
Member

sbatten commented Aug 28, 2019

@isidorn I see your points. I attempted store the editor state and use it on launch but because of other eventing, the editor area gets restored anyway. I need to look more deeply to get the right fix for this. In the interim, I have pushed a fix that stores the editor visibility and uses that to set the panel back to its pre-maximized state.

@isidorn
Copy link
Contributor Author

isidorn commented Aug 29, 2019

@sbatten thanks. That's fair. I do not think this is urgent for August. We can always look into it next milestone when we have more time.

@alexdima alexdima modified the milestones: August 2019, September 2019 Aug 29, 2019
@Tyriar
Copy link
Member

Tyriar commented Sep 6, 2019

Though I would love to hear the opinion from @Tyriar since he is very passionate about this

I think the main users this would help right now are those that want to use a window as a dedicated terminal window which isn't me. However, it would be very useful when we get into the business of restoring terminals across sessions if they are the same size. Even better if the panel is correctly positioned right from the beginning before the terminal starts up.

@konstlepa
Copy link

Also instread of reload you can toggle panel visibility via ctrl/cmd + j. That should aslo preserve the maximized panel

It doesn't preserve the original panel's size😔
fullscreen-bug

This bug is very annoying because I use the shortcut cmd-j very often.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
layout General VS Code workbench layout issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants