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

Vibrancy extension abandoned? #128

Open
mkanet opened this issue Nov 28, 2021 · 2 comments
Open

Vibrancy extension abandoned? #128

mkanet opened this issue Nov 28, 2021 · 2 comments

Comments

@mkanet
Copy link

mkanet commented Nov 28, 2021

@EYHN , is the Vibrancy extension completely abandoned? If so, can you please make an official statement so people don't keep opening new issues? There are several people who depend on this extension.

The last time Vibrancy worked correctly was with VSCode 1.56.1. All newer versions of VSCode cause flickering each time the VSCode app is moved on the screen, resized, etc.; which makes it unusable.

I'm still stuck using VSCode 1.56.1 on all my PCs.

@igor10k
Copy link

igor10k commented Jan 5, 2022

There's no need to complain about that in every issue or create new ones. The author created an issue in the electron's repo long time and can't fix anything until the change is done on the their side. electron/electron#25513
If you depend so much on this extension you can spend some of your time creating a PR there that would allow setting vibrancyVisualEffect on runtime.

@mkanet
Copy link
Author

mkanet commented Jan 5, 2022

Thanks for letting us know. I had no idea the author created an issue on Election; as there was no response from the author to any recent issues (not just the issues I had opened). If it was clear that was the case, I would not have kept trying to get the authors attention... nor would anyone else.
It would be a good idea to update the Readme for Vibrancy to reflect that to avoid other people also opening any further issues here.

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

2 participants