Skip to content
This repository has been archived by the owner on Aug 23, 2022. It is now read-only.

Resize to smallest window bug in VS Code 1.57 #109

Open
IgnusG opened this issue Jun 15, 2021 · 9 comments
Open

Resize to smallest window bug in VS Code 1.57 #109

IgnusG opened this issue Jun 15, 2021 · 9 comments

Comments

@IgnusG
Copy link

IgnusG commented Jun 15, 2021

There seems to be something causing VS Code to resize to the smallest window size when dragging by the title bar - so it looks like this:

image

This only happens in 1.57 in both vibrancy 1.0.15 and 1.0.16-rc1 (the latter one does seem to fix #106, #107, #108).

@IgnusG IgnusG changed the title Resize Bug in VS Code 1.57 Resize to smallest window bug in VS Code 1.57 Jun 15, 2021
@EYHN
Copy link
Owner

EYHN commented Jun 15, 2021

I can't reproduce this problem on my computer, maybe you can record or describe how to reproduce it.

@IgnusG
Copy link
Author

IgnusG commented Jun 15, 2021

Let me know if any logs of some sort would help.

tapex_2021-06-15_16-55-37.mp4

@EYHN
Copy link
Owner

EYHN commented Jun 16, 2021

Thanks for the demo video, I'm sorry there is no such log.
I need you to provide your windows 10 system version and if you have software running on your system about mouse or window control, maybe something like autohotkey

@IgnusG
Copy link
Author

IgnusG commented Jun 16, 2021

I'm on 21H1 (Build 19043.1055). It's an almost blank windows installation without anything like autohotkey.

@exzenous
Copy link

exzenous commented Aug 6, 2021

In my situation, it happens only on non-100% scaling DPI. The problem exists where I drag VS Code window in internal Surface display which has 200% scaling DPI whereas my external display has 100% scaling DPI.
I'm running Windows 11 Build 22000.120 with VS Code 1.59.0
Attached video showing 200% scaling and then 100% scaling

2021-08-06.13-56-47-1.mp4

@IgnusG
Copy link
Author

IgnusG commented Aug 6, 2021

I can confirm I do have scaling set to 175%

@Shir0ha
Copy link

Shir0ha commented Aug 15, 2021

window.getBounds() mess up on my pc

try remove / electron.screen.getDisplayMatching(basisBounds).scaleFactor at https://github.com/EYHN/vscode-vibrancy/blob/733a07104e6f6666aed228447f88d3c00a88f218/runtime/win10refresh.js#L181 and see if it works

Path here if you don't wanna repack %userprofile%\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vscode-vibrancy-runtime-v6

With the latest VSCode (1.61.2) and Vibrancy (v1.0.16), the folder changed to
%userprofile%\.vscode\extensions\eyhn.vscode-vibrancy-1.0.16\runtime

@exzenous
Copy link

window.getBounds() mess up on my pc

try remove / electron.screen.getDisplayMatching(basisBounds).scaleFactor at https://github.com/EYHN/vscode-vibrancy/blob/733a07104e6f6666aed228447f88d3c00a88f218/runtime/win10refresh.js#L181 and see if it works

Path here if you don't wanna repack %userprofile%\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vscode-vibrancy-runtime-v6

That works!

Img1113-1-1.mp4

@th3jesta
Copy link

This is also happening to me on Windows 11, any build. DPI is set to 300%.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants