Faster read/write file performance for remote scenarios You can check out this query of text rendering issues to view progress. We plan to improve font rendering in even more parts of the workbench. In particular, many tree and list elements of the workbench were rendered using greyscale antialiasing and they now render with subpixel antialiasing. The screenshots below show a before and after comparison (zoomed in to show the difference). In this release, we improved font rendering in more parts of the workbench (for Windows and Linux). However, other areas in the workbench still suffered from less than ideal font rendering. We immediately addressed the issue in the editor and the fix was made available in a 1.40 recovery release. Specifically, fonts did not render as smoothly as they used to. When we updated to Electron 6 last milestone, many users reported that font rendering regressed for them. Theme: GitHub Sharp Dark, Font: FiraCode Improved font rendering (Windows, Linux) ![]() The filter box in the Problems panel now adjusts its position according to the panel's position and size. Note: Enabling this feature needs enabling the setting problems.showCurrentInStatus. This allows you to see the summary of the selected problem in the active file without any additional keyboard or mouse gestures. You can now configure VS Code to show the current problem message in the Status bar. You can now filter problems by type (errors, warnings, and information) and also see problems scoped to the current active file. More predefined filters were added to the Problems panel. If you bring up a Peek view and type into it, you can now save changes via ⌘S (Windows, Linux Ctrl+S), if the focus is inside that embedded editor. Note: You can enable Auto Save ( File > Auto Save) if you are tired of pressing ⌘S (Windows, Linux Ctrl+S). If you compare two editors that are editable (for example, from the File Explorer by comparing two files or running a global Search & Replace), the left-hand side is now also editable and can be saved ( ⌘S (Windows, Linux Ctrl+S)). Setting pactFolders controls this behavior. Useful for Java package structures, for example. In such a form, single child folders will be compressed in a combined tree element. In the File Explorer, we now render single child folders in a compact form. ![]() And for the latest Visual Studio Code news, updates, and content, follow us on Twitter Workbench Compact folders in Explorer Insiders: Want to see new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available. If you'd like to read these release notes online, go to Updates on. Dev Containers extension - Better support for opening repositories in Docker containers. ![]() Extract interface refactoring - Quickly extract an inline type to a TypeScript interface.operator to simplify working with nested structures. Optional chaining in JS/TS - Use the ?.HTML mirror cursor in tags - Automatic multi-cursor in matching HTML tags.Terminal minimum contrast ratio - Set preferred contrast ratio for increased visibility.Minimap highlights errors and content changes - Quickly locate problems and changes in your file.Problems panel improvements - Filter by problem type and limit output to the active file.Update search results while typing - Global search results update while you type.Edit left side of diff views - You can now edit both files in a difference view.Compact folders in Explorer - Single child folders collapsed by default.There are a number of updates in this version that we hope you will like, some of the key highlights include: Welcome to the November 2019 release of Visual Studio Code. Update 1.41.1: The update addresses these issues.ĭownloads: Windows: 圆4 | Mac: Intel | Linux: deb rpm tarball snap
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |