- 16 11月, 2019 3 次提交
-
-
由 Alexandru Dima 提交于
-
由 Alexandru Dima 提交于
-
由 Alexandru Dima 提交于
-
- 15 11月, 2019 2 次提交
-
-
由 Alexandru Dima 提交于
-
由 Alexandru Dima 提交于
-
- 14 11月, 2019 2 次提交
-
-
由 Johannes Rieken 提交于
-
由 Johannes Rieken 提交于
-
- 06 11月, 2019 1 次提交
-
-
由 Rachel Macfarlane 提交于
-
- 25 10月, 2019 1 次提交
-
-
由 Peng Lyu 提交于
-
- 24 10月, 2019 3 次提交
-
-
由 Johannes Rieken 提交于
-
由 Alex Dima 提交于
-
由 Alex Dima 提交于
Fixes #50163: Prefer end view position instead of next line's start view position when converting single-line model ranges
-
- 23 10月, 2019 2 次提交
- 19 10月, 2019 1 次提交
-
-
由 Jeremy Shore 提交于
-
- 18 10月, 2019 5 次提交
-
-
由 Alexandru Dima 提交于
-
由 Alexandru Dima 提交于
Revert "`getActiveCodeEditor` should return undefined instead of null" Revert "Make `getFocusedCodeEditor` return undefined instead of null" This reverts commit db11576d. This reverts commit 0fdba099. This reverts commit b18ef0e7
-
由 Alexandru Dima 提交于
This reverts commit 40e0f496.
-
由 Alex Dima 提交于
-
由 Alex Dima 提交于
-
- 17 10月, 2019 5 次提交
-
-
由 Alexandru Dima 提交于
-
由 Alexandru Dima 提交于
-
由 Alex Dima 提交于
-
由 Alex Dima 提交于
-
由 Alex Dima 提交于
-
- 16 10月, 2019 5 次提交
- 15 10月, 2019 1 次提交
-
-
由 Connor Peet 提交于
* minimap - allow variable scaling This PR allows the minimap to be scaled to several constant values. Most of the work in this PR is adjusting the the font renderer to render character at variable sizes. It turns out most generic image scaling algorithms are not built to scale down to one or two pixels (the default minimap font size has 1px by 2px characters), so some work was needed to make this possible and look good. Generating fonts at runtime does incur a small performance penalty, taking about 0.6m at 1x scale and 0.9ms at 4x scale on my machine to create the font the first time we render a minimap. If we want to avoid this, we could consider shipping pre-rendered font for the first few scale settings. At this moment this only supports scaling to a constant integer--effectively, scaling the character width, since we start at 1x2px. More granular scaling would be interesting, but will come at a runtime cost as we'll need to do linear interpolation for each character we draw at a non-integral coordinate. Draw speed is comparable to the previous version, the profiler reported in the range of 8-11ms to render my test file in both the previous and new code. I've tested this on my high DPI Macbook display and it appears to work well there too. Talking to Alex, something we may need to look into is matching the user font and render settings. Previously, and continuing in this PR, we use the default monospace font on the system with a restricted set of character codes. Previously the sidebar's font was too small to be visible, but now its content can be seen under large settings. We may need to look and reworking how this data is rendered. Perhaps we generate the characters we need on the fly into their own buffers? Open to ideas. Fixes https://github.com/microsoft/vscode/issues/21773 * fixup! not caching created factory * fix common/browser component layering * fixup! use a constant upscale for hDPI * small tweaks * fixup! pr comments * fixup! reduce max minimap scale
-
- 12 10月, 2019 1 次提交
-
-
由 Alex Dima 提交于
-
- 11 10月, 2019 1 次提交
-
-
由 Alexandru Dima 提交于
-
- 10 10月, 2019 2 次提交
-
-
由 Alex Dima 提交于
-
由 Rob Lourens 提交于
-
- 09 10月, 2019 1 次提交
-
-
由 Alex Dima 提交于
-
- 08 10月, 2019 4 次提交
-
-
由 Alexandru Dima 提交于
-
由 Martin Aeschlimann 提交于
-
由 Matt Bierner 提交于
-
由 Matt Bierner 提交于
-