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

feat(window): add setEffects API #392

Merged
merged 5 commits into from
Jun 18, 2023
Merged

feat(window): add setEffects API #392

merged 5 commits into from
Jun 18, 2023

Conversation

lucasfernog
Copy link
Member

Ref tauri-apps/tauri#6442

Needs alpha.10 :)

@@ -71,6 +71,11 @@ pub fn run() {
.decorations(false);
}

#[cfg(target_os = "macos")]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not windows as well?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Windows is already handled on the block above.

*
* @since 2.0
*/
async clearEffects(): Promise<void> {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we add an explicit clear effects method on tauri's side? Instead of relying on None?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think setting None is quite idiomatic for Rust isn't it? For JavaScript it looks weird..

@lucasfernog lucasfernog marked this pull request as ready for review June 17, 2023 22:00
@lucasfernog lucasfernog requested a review from a team as a code owner June 17, 2023 22:00
@lucasfernog lucasfernog merged commit c8c3191 into v2 Jun 18, 2023
@lucasfernog lucasfernog deleted the feat/window-effects branch June 18, 2023 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants