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

change the "visualEffectState" option at runtime #25513

Open
3 tasks done
EYHN opened this issue Sep 17, 2020 · 8 comments
Open
3 tasks done

change the "visualEffectState" option at runtime #25513

EYHN opened this issue Sep 17, 2020 · 8 comments

Comments

@EYHN
Copy link

EYHN commented Sep 17, 2020

Preflight Checklist

  • I have read the Contributing Guidelines for this project.
  • I agree to follow the Code of Conduct that this project adheres to.
  • I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Problem Description

Since #24471 #25083 , BrowserWindow adds an option "visualEffectState" that allows us to customize the app visual effect state be inactive or active regardless of window activation state.

Just like we have BrowserWindow.setVibrancy(type) which can change the vibrancy effect of the application at runtime.

I hope to have a "BrowserWindow.setVisualEffectState(state)" method to change the "visualEffectState" option at runtime.

Additional Information

EYHN/vscode-vibrancy#67

@eatinsnacks
Copy link

I could benefit from this too.

@eatinsnacks
Copy link

Still interested in this.

@AurevoirXavier
Copy link

Still interested in this.

+1

@florius0
Copy link

florius0 commented May 3, 2022

+1

2 similar comments
@Dessader
Copy link

+1

@djklu31
Copy link

djklu31 commented Oct 11, 2022

+1

@foxt
Copy link
Contributor

foxt commented Aug 31, 2023

Yeah, it doesn't make sense to have there be a disabled option if you can only apply it at init time.

@mayurankv
Copy link

I'd also love this!

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

No branches or pull requests

9 participants