Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: First-time use notification and defaults not working on VSCodium #156

Open
1 task done
Saya47 opened this issue Aug 8, 2024 · 5 comments
Open
1 task done
Labels
bug Something isn't working

Comments

@Saya47
Copy link

Saya47 commented Aug 8, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

image

Expected Behavior

For it to actually work! It did not even prompt me to install the extension in notifications, I keep reloading and enabling and it does not work.

Steps To Reproduce

On Windows 11, install VSCodium with Scoop then install Vibrancy Continued.

Environment

- OS: Windows 11
- VSCode: VSCodium 1.91.1.24193 installed through Scoop
- Extension: no other extensions
- Theme: Dark+/Tokyo

Anything else?

Thanks for your beautiful work!

@Saya47 Saya47 added bug Something isn't working triage Cause of the issue needs to be triaged labels Aug 8, 2024
@illixion
Copy link
Owner

illixion commented Aug 8, 2024

I'll have to check why you didn't receive a first-time use notification, but regarding the issue, I can see that your window controls in the top right are differently colored which means that Vibrancy is applied. It's likely that you have transparency effects disabled globally via the "Transparency effects" Windows setting or some power-saving mode. Also, if you've changed the Vibrancy transparency type to an incompatible one, that could also cause this.

@Saya47
Copy link
Author

Saya47 commented Aug 8, 2024

Thank you for the reply! I did not change any settings, everything is default, but since you mentioned, I also tried these two:
image

I enabled global transparency effects but nothing changed unfortunately.
image

image

I do not like Windows transparency effects for all windows btw, I want transparency for VSCodium only!

And I'm on high performance:
image

I wish you added the possibility to reinstall or uninstall Vibrancy through command pallet because not matter how many times I try to uninstall and reinstall the extension from the marketplace, I do not get the install vibrancy notification!

@illixion
Copy link
Owner

illixion commented Aug 8, 2024

I enabled global transparency effects but nothing changed unfortunately.

The VSCode window in your screenshot looks different, and I think it already has a transparency effect, what is your Vibrancy opacity set to?

I do not like Windows transparency effects for all windows btw, I want transparency for VSCodium only!

Unfortunately, the setting you're using is a system-wide on/off switch, and Electron respects it. Perhaps you can find some third-party tool that can achieve what you're looking for.

I wish you added the possibility to reinstall or uninstall Vibrancy through command pallet because not matter how many times I try to uninstall and reinstall the extension from the marketplace, I do not get the install vibrancy notification!

You can, the actions are called "Enable Vibrancy", "Reload Vibrancy" and "Disable Vibrancy"

@Saya47
Copy link
Author

Saya47 commented Aug 8, 2024

ohhhh there was no number assigned to it by default, I enabled it and it seems to be working now!
I also enabled Tokyo theme and look at it now!
image
It's amazing thanks so much!
I should also note that I can resize and move my VSCodium, but I can't maximize or snap which imo is fine :D

@illixion
Copy link
Owner

illixion commented Aug 9, 2024

Glad to hear! I'll look into the opacity issue as well, it's unusual that the default wasn't applied.

@illixion illixion changed the title [Bug]: Does not work on VSCodium installed with Scoop [Bug]: First-time use notification and defaults not working on VSCodium Aug 9, 2024
@illixion illixion removed the triage Cause of the issue needs to be triaged label Aug 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants