visual studio code looks blurry - visual-studio-code

Folks, this is not a code question but I dont know where else to post this. the website of VS Code linked me here so here goes.
Here are my visual studio code version details
Version: 1.26.1
Commit: 493869ee8e8a846b0855873886fc79d480d342de
Date: 2018-08-16T18:38:57.434Z
Electron: 2.0.5
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64
Once I updated to this version, the entire app started looking blurry. It was fine before the update and has been looking fine on this windows 10 machine.
I got other Microsoft Apps - Office Word, Excel and the rest, and they all fine. Visual Studio (regular) looks fine. Its this software and only since the latest update to 1.26.1
Note: There is one other software which always had a blurry appearance, and that is Postman. I assumed that it is a Postman issue so never got around to fixing it or try fixing. adding this here if there is a connection but the question is primarily about Code, and how I could fix the appearance problem.
Update 1 :
So, I opened Postman and that also has stopped being blurry. So, looks like the blame does fall on AMD Radeon rather than MS or Postman developers.

NVIDIA Control Panel
Manage 3D settings
Program Settings
Select VS Code from dropdown or add it if it's not there
Set "Antialiasing - FXAA" to OFF
https://www.reddit.com/r/vscode/comments/9szgkp/visual_studio_code_blurry/

I know this is late but just in case it didn't work for someone, here is another solution:
Right click on VsCode and go to properties.
Copy this command
--disable-gpu --enable-use-zoom-for-dsf
and append it to the target path n the shortcut properties dialog.
Click apply and the reopen VScode.
Here is the article that I am referencing https://medium.com/kasun-kodagoda/fix-text-becomes-blurry-when-vs-code-application-loses-focus-issue-on-windows-d95697b2f927

Try turning Off Anti-Aliasing in your Graphics Settings.Since it Over Renders the Text.

Go into your settings and type "rendering" you should see "Terminal > Integrated: Gpu Acceleration" if you turn if off it should fix the problem.

Go to settings.json and add - "terminal.integrated.gpuAcceleration": "off"

I have a problem every now and then where just the terminal gets blurry. I simply zoom in and zoom out ("⌘=", "⌘-") and it fixes them problem.

For AMD:
Open AMD Radeon Software Panel
Go to Settings > Graphics Tab > Advance Settings > Morphological Anti-Aliasing (x) disable this option.
IMAGE LINK

First of all please accept my apologize for not responding so soon, I
am afraid I can't provide you with a feedback because the issue were
my AMD Radeon Graphics Drivers, after an Update was released the issue
was gone. Thanks for your hard work!
Read this comment on github.
It is possible that there is some kind of an issue with your Graphic card, try updating your Graphic card drivers.

I tried updating my drivers as suggested by Yashu Mittal without any luck. After some tinkering I realized that it is because I had set Anti-Aliasing to something other than "application control" in my graphics card settings.

For those who have a similar issue but in Visual Studio IDE (currently, I am using 2019 edition).
Go to "Tools -> Options -> General", and turn on "Optimize rendering for screens with different pixel densities"
link to the settings image

Related

Unity Editor does not fully render UI and is unresponsive on Windows 10

The editor window does not fully render and is unresponsive... I restored windows by completely reinstalling it, fresh install, all clean... and still same issue:
I checked Unity 2017.3, 2017.2 and 5.6, with DX9, 11 and 12... allways same issue.
I found 0 related issues on google, maybe I'm not using the correct wording for the search (Unresponsive Unity Editor Windows). On the Unity forums someone mentioned DX version being the issue, but I already forced all recent versions and it fails for all of them.
Ok, so the issue is with Unity not being dpi aware so I had to remove my 150% scaling on my main 4K window in order for it to work.
Unity programmers my encounter this issue too, and come here for help as I did... I don't see why that's wrong #Programmer

My Visual studio 2013 typing and scrolling is slow. What Can i do?

I'm Currently working on Visual studio 2013 (MVC 5). Since few days I'm getting a problem with typing and scrolling, database is connecting slow. But all working fine but slowly.
Problems:
When typing a letter that keyword display taking long time and some
times not displayed.
Scrolling the solution explorer does not response correctly.
Connect the Database is not showing the connection string.
I searched on the internet and found smooth scroll plugin. After installing that it worked for some hours only after that getting same problem
Apart from Visual Studio 2013 Update 5 which will play an important role here you can also check other solutions listed below.
For smooth scrolling you could try the below steps :
For smooth scrolling install this extension
In VS Go Tools > Environment > General.
My Install had the "Automatically adjust visual experience based on client performance" checked which was using software-accelerated rendering. I unchecked this and checked "Use hardware graphics acceleration if available".
Restart VS
Slow building, debugging, navigating ?
Why is VS 2013 very slow?
More references :
MSDN
You need to check two things: CPU load and drive load. Open the Task Manager and observe the CPU load to determine if the problem is due to the CPU is being overloaded. Watch the HDD LED to see if it flashing rapidly or on and solid to see if the problem is due to the hard-drive is being thrashed (and thus overloaded). Both can cause this symptom. If you find either to be the case, then your next step is to figure out why the system is being burdened.
if 0% CPU and 0% disk. But any text editing heavily lags? Must be due to some sort of plugin or something. I know the CodeLens, Insights, and Microsoft Git have had issues reported with slow IDE response.
Also try disabling Synchronized Settings in VS. Go to Tools -> Options -> Environment-Synchronized Settings and remove this option by un-checking the check box.
Update your Visual Studio get working normally.
https://www.visualstudio.com/en-us/news/vs2013-update5-vs.aspx

AutoComplete dissapears when importing typescript module namespace in vs 2013

Imagine:
Ok, so in vs 2013 (update 2) this works fine, no red squiggles or anything. But in the "OtherClass", when writing "im.", i get no auto-complete with suggestions of "MyInterface", as I would expect.
If i write something that does not exist in the namespace, the red squiggles appear. So some kind of intellisense exist.
If I however skip the "import" part and write the whole namespace: "foo.bar.a." I get auto-complete all the way and suggestion of MyInterface at the end.
I would like to use the import syntax to get shorter lines, but if I won't get auto-complete, suggestions, it's not worth it.
Does anyone have a solution for this? Getting the auto-complete while using import i mean.
Thanks!
The interface is auto generated by web essentials from a c# model, if that would help.
Update
Ok, so I found a setting under Tools -> Text Editor -> Typescript -> General
called "Auto list members". It was unchecked so I checked it and it does come up with the suggestion, but, it looks weird.
If you look closely you see that the suggestion is sort of on top of other the suggestions. Even in the second case which worked fine before. It does look like the screen shot Steve Fenton took, with the small white down arrow under the blue thing(an arrow that does not show for me when writing entire namespace in the First case), so I guess he might have this option checked. But it seems for me it does not work as well.
Update 2
Ok so the thief was resharper. Sorry I forgot to mention i used it.
I fixed it by changing to use vs 2013 Auto list members for typescript and shut it off for resharper like so: http://www.cloud-developer.eu/blog/2013/12/03/solved-intellisense-working-typescript-resharper-installed-using-visual-studio-2012/
But i checked "Visual Studio", instead of "Limited ReSharper Intellisense"
It works for me™, which suggests one of the following...
It could be a problem with the language service. This normally resolves when you close and re-open the file or when you restart Visual Studio.
If this isn't the case, it may be a bug in Visual Studio - something is making it mess up. You will almost certainly be asked to uninstall/reinstall before anyone will look at your bug, so do that if you still have a problem and see if it fixes it.
If neither of these help, it will be time to raise a bug for Visual Studio :(
Here is my screen shot of the working code:
Ok, as I stated it seems it was ReSharper intellisense vs Visual Studio 2013 intellisense.
The link under my Update 2 was a fine solution for me before, when I had Resharper 8.1 installed.
But it seems they have improved it and in 8.2 the original issue is fixed. So I have now unchecked the "auto list members" in vs2013 options and only use resharper.
I got the same problem using VS2013 and Resharper 8.2 but this was due to a error on my side in the path to the module I required. So I guess there is a bug that misses the error from my side...

IE11 F12 Developer Tools on Windows 7 functionality missing/not working?

I was using IE10 on Windows 7 but it is such a buggy piece of you-know-what (hanging, crashing, etc.) that I gave up and installed IE11. It has not hung or crashed since installing. But I hate the F12 developer tools! Okay, not completely - there are some very cool new features. What I don't like is that they seem to have dropped several features that I really liked! Unless I'm just missing something... I've searched and searched on Google and Microsoft but all of the help I've found only describes the new features. Here is what I'm missing: Color picker, Ruler, and most of all, the Clear browser cache for this domain. They allege to have a Clear browser cache function, but it doesn't work! So when I make changes to my website, in particular changing graphics, the only way I can see the change is to delete all my temporary files from IE. Then I lose all of my cookies e.g. for automatically logging in to Stack Overflow! IE version 11.0.9600.16428 on Windows 7 Ultimate 64-bit.
The color picker is still available, go to the DOM Explorer tab and there is an eye dropper on the tool bar at the top towards the left. That activates the color picker.
For the issue of serving cached files try toggling on "Always refresh from server" on the network tool (3rd option from the left). This should get you the latest changes from your server.

Minimize floating windows in NetBeans 7.2

I recently upgraded to NetBeans 7.2 and am facing a substantial usability issue with floating windows. In 7.1 each floating window was minimize-able, which I used quite regularly. By all appearances the minimize button is completely gone. The button is missing and when I right click on the title bar, the close button is available but the minimize is disabled (greyed out).
I'm running windows 7 x64.
I also encountered the issue in the RC but figured that it would be resolve in the final version. I've googled around and not been able to find anyone with the same issue so I'm hoping that it is just me.
I checked out the settings under Tools > Options > Miscellaneous > Windows and none of them seem to make any difference.
How can I get the minimize floating windows functionality back?
It looks like a bug on the windows version, because I'm using the mac one and the minimize buttons are in place.
I'd go back to the previous version until they solve the bug.
In fact, at least in mac, you can have both versions installed, so you could open 7.2 from time to time and check for any updates that solved the problem.
I've found some additional info here:
https://netbeans.org/bugzilla/show_bug.cgi?id=216019
Maybe you could try to do as they tell:
No minimize button means those windows are docked into editor docking spot. Use
menu Window - Reset Windows.
I am able to minimize windows in netbeans on win 7x64
And sorry I wanted to add this as a comment, but apparently I couldn't