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

Workspace Button doesn't always show up #1219

Closed
SchweizS opened this issue May 6, 2020 · 4 comments
Closed

Workspace Button doesn't always show up #1219

SchweizS opened this issue May 6, 2020 · 4 comments
Labels
more info needed More info is needed from the community for us to properly triage and investigate. stale to use with the close-stale-issues bot

Comments

@SchweizS
Copy link
Contributor

SchweizS commented May 6, 2020

Brief Issue Summary

Workspace Button doesn't show up in Statusbar if a second directory is added to a workspace.

workaround

Reopen VS-Code after adding a second directory

Expected:

Workspace Button gets visible

Apparent Behavior:

Workspace Button is hidden.

Reproduction steps

  1. create a new workspace (only one directory)
  2. add a second directory to that workspace
  3. check if the button is visible

Platform and Versions

  • Operating System: Windows 10
  • CMake Version: 3.17.0
  • VSCode Version: 1.44.2
  • CMake Tools Extension Version: 0ee9aaf 1.3.1

Other Notes/Information

#1200

@andreeis
Copy link
Contributor

andreeis commented May 6, 2020

I am not able to reproduce the missing button. Your description is good and clear, I understand it. I tried several ways that could fit the above steps. Let's figure out if maybe a trigger factor is missing from the repro scenario.

@andreeis andreeis added the more info needed More info is needed from the community for us to properly triage and investigate. label May 6, 2020
@SchweizS
Copy link
Contributor Author

SchweizS commented May 7, 2020

i don't know what i did differently yesterday, but all 3 versions i tried it with work today. (dev/1.3.1/#1200)

i'll try to find the trigger as soon as i'm able to reproduce it myself again.

@github-actions
Copy link

This issue is now marked as 'stale' due to there being no activity on it for the past 30 days and being labelled 'more info needed'. Unless the 'stale' label is removed or the issue is commented on, this will be closed in 7 days. If you would like to make this issue exempt from getting stale, please remove the 'more info needed' and 'stale' labels or add the 'stale-exempt' label

@github-actions github-actions bot added the stale to use with the close-stale-issues bot label Oct 18, 2023
@github-actions
Copy link

This issue is now closed due to there being no activity on it for the past 7 days since being marked as 'stale'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
more info needed More info is needed from the community for us to properly triage and investigate. stale to use with the close-stale-issues bot
Projects
None yet
Development

No branches or pull requests

2 participants