You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a Teamwork passion project and not officially supported by the team
The creators and maintainers of this project are doing it with enthusiasm and happiness, in odd moments between other projects and possibly even in their spare time. Please be kind to them, and understand that although they hope to get the time & energy to fix your bug 🤞, this is not an officially supported product or service, and therefore doing so is not a part of their day jobs.
Describe the bug
This was previously sent to the team via email but wanted to add here just in case other run into the same issue as I had. One of my colleagues had this same problem today and I helped them troubleshoot it which prompted me to want to share.
Wanted to give you an update on this issue that I was/still am having with the plugin. I had to reinstall windows on my work laptop yesterday and with a new install of VSCODE I wanted to give the TW plugin a go in a clean environment and see if it would work for me like it was supposed to, sure enough it did. So I logged into the account I use for my settings sync and once everything matched how they are on my primary computer I tried the plugin again and it was still working. Did a restart, all other updates to confirm it wouldn’t break and to my surprise everything was functioning as intended.
So back over on my main computer, I uninstalled the plugin, removed all settings and even went through my list of plugins and nixed a bunch of ones I no longer needed anymore and then did clean install of the TW plugin again. Tried opening a task and it did the same thing it had been doing previously, shows the please wait loading window but never loads the task.
That got me to thinking about what other differences there were between my main computer and the laptop and the biggest difference is that on my primary computer I use an Ultrawide monitor with a resolution of 3440X1440. So I tried changing the resolution to what I use for client calls/screenshare which is 2560X1440 and sure enough, it worked! I have built some VSCode plugins in the past but nothing that integrates a window like yours does but Im wondering if there is some sort of scaling option that is available that might be the source of the issue on UltraWide Resolutions? I also tested plugging my monitor into my laptop and it immediately had the exact same issue.
Thanks in advance, wanted to give you an update in case others might have the same issue.
To Reproduce
Steps to reproduce the behavior:
Error happens on screen resolutions higher than 1080P in my case.
Selecting a project from the left hand menu causes the loading panel on the right to appear and shows that it is loading the content but it never finishes.
If you change your resolution to something less than 1080P, the right hand menu loads just fine.
Expected behavior
A clear and concise description of what you expected to happen.
Desktop (please complete the following information):
OS: Windows 11
Version [e.g. 22]
Additional context
Team already responded that they were aware of the issue, sharing in case other users run into the same issue
The text was updated successfully, but these errors were encountered:
This is a Teamwork passion project and not officially supported by the team
The creators and maintainers of this project are doing it with enthusiasm and happiness, in odd moments between other projects and possibly even in their spare time. Please be kind to them, and understand that although they hope to get the time & energy to fix your bug 🤞, this is not an officially supported product or service, and therefore doing so is not a part of their day jobs.
Describe the bug
This was previously sent to the team via email but wanted to add here just in case other run into the same issue as I had. One of my colleagues had this same problem today and I helped them troubleshoot it which prompted me to want to share.
Wanted to give you an update on this issue that I was/still am having with the plugin. I had to reinstall windows on my work laptop yesterday and with a new install of VSCODE I wanted to give the TW plugin a go in a clean environment and see if it would work for me like it was supposed to, sure enough it did. So I logged into the account I use for my settings sync and once everything matched how they are on my primary computer I tried the plugin again and it was still working. Did a restart, all other updates to confirm it wouldn’t break and to my surprise everything was functioning as intended.
So back over on my main computer, I uninstalled the plugin, removed all settings and even went through my list of plugins and nixed a bunch of ones I no longer needed anymore and then did clean install of the TW plugin again. Tried opening a task and it did the same thing it had been doing previously, shows the please wait loading window but never loads the task.
That got me to thinking about what other differences there were between my main computer and the laptop and the biggest difference is that on my primary computer I use an Ultrawide monitor with a resolution of 3440X1440. So I tried changing the resolution to what I use for client calls/screenshare which is 2560X1440 and sure enough, it worked! I have built some VSCode plugins in the past but nothing that integrates a window like yours does but Im wondering if there is some sort of scaling option that is available that might be the source of the issue on UltraWide Resolutions? I also tested plugging my monitor into my laptop and it immediately had the exact same issue.
Thanks in advance, wanted to give you an update in case others might have the same issue.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Desktop (please complete the following information):
Additional context
Team already responded that they were aware of the issue, sharing in case other users run into the same issue
The text was updated successfully, but these errors were encountered: