Vscode-vibrancy: Acrylic not functioning as expected, appears for second then disappears 1.0.15

Thank you for reporting the problem, I will look into it as soon as possible, until then please use vscode 1.56.2.

Yeah, I'm having this same issue in 1.57.0 insider

same here, 1.57.0

It looks like this issue has also reached the regular non-insider build too. v1.57.0

I'm still researching the cause of this issue.

For everyone who having problem with version 1.57.0,

Please stop complaining its not working and let the man work out on it.
He literally commented use version 1.56.2 until he updates the extension.

Jesus..

I'm also running into the same issue with macOS. I don't think it is Windows only. And yes, JorDindi is right, just downgrade until a fix is done.

Hi, I have fixed this problem in vscode-vibrancy 1.0.16-rc1.
I have not released it in the vscode extension marketplace. You can download the .vsix from here and install it manually.
https://github.com/EYHN/vscode-vibrancy/releases/tag/1.0.16-rc1

I will publish the version in the vscode extension marketplace when the test is complete.

Hi, I have fixed this problem and make sure you have upgraded this extension to v1.0.16.

If the problem is not resolved, please update this issue.

@EYHN there seems to be an odd issue with this fix. When I resize the window, the transparent background briefly switches to a weird transparent light color. It does this every time. The same way it does when first starting VSCode with Vibrancy enabled. It didn't use to do this before.

It is kind of a clunky transition every time... window.setBackgroundColor("#00000000"); seems to happen each time VSCode window resizes (or sometimes when the window is moved); which is very distracting.

Is there a way to prevent updateBackgroundColor from happening each time the window resizes?

@mkanet
I think there is indeed this problem
I also found that he would appear temporarily opaque

@mkanet @shoucandanghehe The current solution does have flickering problems and I am looking for a better solution.

I'm curious, is there a reason why this issue is closed?

I'm curious, is there a reason why this issue is closed?

The original issue is fixed I assume. The new issue with the solution is that it sometimes flickers in and out so maybe a new issue thread would be good @EYHN?

Hi @EYHN I'm still stuck on VSCode Version 1.56.1 on all my PC's since newer versions of VSCode don't display properly with Vibrancy 1.0.16-rc1. Any luck fixing the flickering problem?
Unfortunately, the flickering problem is too distracting to use when coding.