Open mkanet opened 2 years ago
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. https://github.com/electron/electron/issues/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.
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.
@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.