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

Sections should remember last state (collapsed or expanded) #149

Closed
OsirisTerje opened this Issue Nov 10, 2015 · 7 comments

Comments

Projects
None yet
3 participants
@OsirisTerje

When one open the Manage Connection hub in Team Explorer, the github node comes up at top, which is fine, but it always comes up expanded, which can be sort of annoying if one wants quickly to see what is further down.
The github node should either: 1) start collapsed or 2) remember if one sets it collapsed or expanded for the next time the same hub is opened.

@shana

This comment has been minimized.

Show comment
Hide comment
@shana

shana Nov 10, 2015

Collaborator

Thanks for the report!

All sections in Team Explorer are expanded by default, but it should definitely remember if it was last expanded or collapsed whenever you go to the Connect hub, so you don't have to keep closing it. I'll add it to the bug list 😊

Collaborator

shana commented Nov 10, 2015

Thanks for the report!

All sections in Team Explorer are expanded by default, but it should definitely remember if it was last expanded or collapsed whenever you go to the Connect hub, so you don't have to keep closing it. I'll add it to the bug list 😊

@shana shana changed the title from Github node always starts expanded to Sections should remember last state (collapsed or expanded) Nov 10, 2015

@shana shana added the bug label Nov 10, 2015

@OsirisTerje

This comment has been minimized.

Show comment
Hide comment
@OsirisTerje

OsirisTerje Nov 10, 2015

Thanks !

One comment to this is that the github node places all repositories in a long list, but they could have been split the same way as TFS does, having a github organisation equal to a Team Project. Then it would be easier to have open only the nodes of interest, the rest collapsed, as one can do with the TFS nodes.

Anyway, having it remember the state, as the Team Project nodes seems to do, will obviously help and make it consistent.

Thanks !

One comment to this is that the github node places all repositories in a long list, but they could have been split the same way as TFS does, having a github organisation equal to a Team Project. Then it would be easier to have open only the nodes of interest, the rest collapsed, as one can do with the TFS nodes.

Anyway, having it remember the state, as the Team Project nodes seems to do, will obviously help and make it consistent.

@shana

This comment has been minimized.

Show comment
Hide comment
@shana

shana Nov 10, 2015

Collaborator

I'm not sure I understand what you mean by having a github organisation equal to a Team Project. Do you mean having separate (collapsable) sections per user/organizations that you're a part of?

Collaborator

shana commented Nov 10, 2015

I'm not sure I understand what you mean by having a github organisation equal to a Team Project. Do you mean having separate (collapsable) sections per user/organizations that you're a part of?

@OsirisTerje

This comment has been minimized.

Show comment
Hide comment

Exactly !

@shana

This comment has been minimized.

Show comment
Hide comment
@shana

shana Nov 11, 2015

Collaborator

Sounds like a great idea!

Collaborator

shana commented Nov 11, 2015

Sounds like a great idea!

@OsirisTerje

This comment has been minimized.

Show comment
Hide comment
@OsirisTerje

OsirisTerje Nov 11, 2015

Should it stay here, or be a separate issue ?

Should it stay here, or be a separate issue ?

@shana

This comment has been minimized.

Show comment
Hide comment
@shana

shana Nov 11, 2015

Collaborator

@OsirisTerje Separate issue, I've logged it 😄

Collaborator

shana commented Nov 11, 2015

@OsirisTerje Separate issue, I've logged it 😄

grokys added a commit that referenced this issue May 5, 2016

Remember section expanded state.
Fixes #149 .

Sections in the Connect pane in Team Explorer now remember their
expanded state between Visual Studio sessions.

@shana shana closed this in #290 May 12, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment